Bug#1022726: Dillo 3.1.1 released

2024-06-09 Thread Rodrigo Arias

Hi Axel,

Yesterday, I have released Dillo 3.1.1 which includes some bug fixes, 
see the release notes here:


https://dillo-browser.github.io/release/3.1.1/

The previous 3.1.0 release has been included in most major repositories
and 3.1.1 is being updated quickly:

https://repology.org/project/dillo/history

I'm no very familiar with Debian packages, but I can try to prepare one
for 3.1.1 if you are open to it.

I saw that you were also on the old mailing list which is now hosted
in mailman3.com, in case you want to take a look and maybe join again:

https://lists.mailman3.com/postorius/lists/dillo-dev.mailman3.com/

Best,
Rodrigo.



Bug#1022726: Dillo 3.1.0 released

2024-05-07 Thread Rodrigo Arias

Hi,

Dillo 3.1.0 has been released a few days ago:

https://dillo-browser.github.io/latest.html

On HN:

https://news.ycombinator.com/item?id=40260035

Now it supports OpenSSL 1.1 and 3, as well as LibreSSL and Mbed TLS 2 
and 3.


The flag --enable-ssl has been renamed to --enable-tls and is set by 
default so is no longer needed, and the following patches shouldn't be 
needed anymore:


- fix-OpenSSL-1.1-detection.patch
- fix-duckduckgo-shortcut-in-dillorc.patch
- fix-FTBFS-with-gcc-10.patch

I assume these are Debian specific:

- fix-perl-shebang.patch
- move-helper-tools-to-libexec.patch

We also install the .desktop file with the Dillo icons from upstream.

For reference, here are the changes in Arch Linux package:

https://gitlab.archlinux.org/archlinux/packaging/packages/dillo/-/commit/ee5f62bb0ce230fe0538359c829fdbb8b7dced3d

And Fedora:

https://src.fedoraproject.org/rpms/dillo/c/25c8726b48a75aadd51214d29e34f9ea6935e1e8?branch=rawhide

Thanks,
Rodrigo.



Bug#1036382: dillo: doesn't recognize XHTML 1.1 as HTML

2024-05-03 Thread Rodrigo Arias

Hi,

On Sun, May 21, 2023 at 11:14:58AM +0200, José Luis González wrote:

On Sun, 21 May 2023 05:34:16 +0200
José Luis González  wrote:


All I ask you is to confirm the bug was not coming from a
Debian patch and forward the full report to upstream. That's all.


Sorry Andrey, I mistook you for the maintainer. You can overlook this,
obviously :)



Thanks for the report José, both bugs have been fixed in PR 140[1].

[1]:https://github.com/dillo-browser/dillo/pull/140

It will be included in Dillo 3.1.0 release.

Regarding the meta tag:





The content type "text/xhtml" have never been standardized and
"application/xhtml+xml" should be used instead (Doxygen still uses it).
There was already a quirk to correct this problem, which was not working
well but is fixed now. If you want to look into the details, take a look
at the patches[2] and/or this thread[3].

[2]:https://patch-diff.githubusercontent.com/raw/dillo-browser/dillo/pull/140.patch
[3]:https://lists.mailman3.com/hyperkitty/list/dillo-...@mailman3.com/thread/7GJ4AAMFFPEHOIYEOH4NHVMSXMJDFYXG/?noscript

Best,
Rodrigo.



Bug#1022726: New Dillo release 3.1.0-rc1

2024-04-13 Thread Rodrigo Arias

Hi,

I've been maintaining Dillo for some months to get the 3.1.0 release 
ready, so it can include some of the changes since 3.0.5 was released 
back in 2015. I'm trying to stick to the original goal, which is to keep 
the browser as simple as posible and support a wide range of systems.


I have created a new website for it, which contains the old website 
files too:


https://dillo-browser.github.io/

I explained what happened to the dillo dot org domain in a post, with a 
bit of background to understand why it happened:


https://dillo-browser.github.io/dillo.org.html

There have been no replies from Jorge, the lead developer of Dillo since 
2019. I have also contacted several developers via alternative emails 
from the commit logs and some of them replied and they have helped me to 
get a backup from the original server for the mailing list archives and 
the website.


The mailing list is now at  and we keep the old 
and new archives here:


https://lists.mailman3.com/postorius/lists/dillo-dev.mailman3.com/

We have made the 3.1.0-rc1 release candidate while we perform the final 
tests before the stable 3.1.0 is release. Please check the release 
notes:


https://dillo-browser.github.io/latest.html

While we build Dillo on Ubuntu and other systems on the GitHub CI, I 
would expect it to work without problems on Debian, but it would be nice 
to get it packaged and tested on a physical system.


If you want to see the details, check the issues/PR or the commit log:

https://github.com/dillo-browser/dillo/milestone/1?closed=1
https://github.com/dillo-browser/dillo/commits/master/

Dillo now allows building TLS support from OpenSSL 3, OpenSSL 1.1, Mbed 
TLS 2, Mbed TLS 3 or LibreSSL. By default, it searches first for 
OpenSSL.


Some of the bugs from your tracker have been fixed, others need a bit 
more time.


For this release, we are mostly fixing bugs. New features from other 
forks like DilloNG may be introduced later.


Thank you for keeping it on the repositories for all these years, 
hopefully we can get a new version soon.


Best regards,
Rodrigo.



Bug#1035110: ITP: drminfo -- Small utility to dump info about DRM devices

2023-04-29 Thread Rodrigo Siqueira
Package: wnpp
Owner: Rodrigo Siqueira 
X-Debbugs-Cc: siqueirajor...@riseup.net
Severity: wishlist

* Package name: drminfo
  Version : 2.4.0 
  Upstream Contact: Simon Ser , Scott Anderson 

* URL : https://gitlab.freedesktop.org/emersion/drm_info
* License : MIT
  Programming Lang: C
  Description : Small utility to dump info about DRM devices

The drm_info is a small tool for getting GPU information such as
supported formats, capabilities, properties, etc. This is a valuable
tool to collect GPU data from the Direct Rendering Manager (DRM)
perspective, which can guide developers and users about some specific
feature support in a GPU. The website https://drmdb.emersion.fr/ is an
example of an extensive database built with the drm_info tool and with
the collaboration of multiple people.

I already have the drminfo package available at:

 https://salsa.debian.org/siqueira/drminfo

Thanks

-- 
Rodrigo Siqueira
https://siqueira.tech


signature.asc
Description: PGP signature


Bug#1016963: Please test u-boot for a64-olinuxino

2022-12-29 Thread rodrigo




On 2022-12-28 21:12, Vagrant Cascadian wrote:

On 2022-12-28, Vagrant Cascadian wrote:

On 2022-12-22, Vagrant Cascadian wrote:

On 2022-08-20, Vagrant Cascadian wrote:

On 2022-08-10, Vagrant Cascadian wrote:
This bug is just to delay migration to testing while more platforms 
get

tested. If you have a relevent board, please consider testing and
reporting the status:

  https://wiki.debian.org/U-boot/Status


I have not received many test results for current or even remotely
recent u-boot platforms in Debian, and u-boot has been blocked from
migration to testing partly because of this.

As the bookworm freeze approaches, this is getting to be... worrysome!

If you have access to any of these boards, please consider testing
u-boot versions as packaged in debian for versions from debian stable
(2021.01*), testing (2022.04*), unstable (2022.10*) and experimental
(2023.01-rc*) and updating the wiki page if successful and/or replying
to 1016...@bugs.debian.org with a positive confirmation...

...and if not successful, filing bugs against the relevent u-boot-*
packages and marking them as blocking 1016963.


a64-olinuxino


Sadly my a64-olinuxino board has died and I'm no longer able to test it.



Bug#1023125: performous: new upstream release (1.2.0)

2022-10-30 Thread Rodrigo Campos

Package: performous
Version: 1.1+git20181118-5+b1
Severity: normal

Hi!

A few months ago there has been a new upstream release of performous for 
version 1.2.0. See:

https://github.com/performous/performous/releases/tag/1.2.0

It would be great to have it in Debian :)



Best,
Rodrigo



Bug#1012179: CVE-2021-46143: Integer overflow in expat can be found on libxmltok

2022-05-31 Thread Rodrigo Figueiredo Zaiden
Package: libxmltok
Version: 1.2-4
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch

Dear Maintainer,

While triaging CVE-2021-46143 for expat, it was found that one part of
the reported integer oveflow, in doProlog() in xmlparse.c, is also
present in libxmltok.
So, I'm suggesting to apply this patch for libxmltok in Debian as well.

In Ubuntu, the attached patch was applied to achieve the following:

  * SECURITY UPDATE: Integer overflow
- debian/patches/CVE-2021-46143.patch: add an integer overflow check
  for groupSize variable at doProlog() in xmlparse/xmlparse.c.
- CVE-2021-46143


Thanks for considering the patch.


-- System Information:
Debian Release: bookworm/sid
  APT prefers jammy-updates
  APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'), 
(100, 'jammy-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-33-generic (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru libxmltok-1.2/debian/patches/CVE-2021-46143.patch 
libxmltok-1.2/debian/patches/CVE-2021-46143.patch
--- libxmltok-1.2/debian/patches/CVE-2021-46143.patch   1969-12-31 
21:00:00.0 -0300
+++ libxmltok-1.2/debian/patches/CVE-2021-46143.patch   2022-05-30 
16:58:54.0 -0300
@@ -0,0 +1,29 @@
+Description: backport of libexpat upstream patch
+ Backport of libexpat patch that is included in libxmltok:
+ Prevent integer overflow on groupSize in function doProlog
+Author: Rodrigo Figueiredo Zaiden 
+Origin: upstream, 
https://github.com/libexpat/libexpat/commit/82c11af9d3dafc1b086a15efecd6ec07b6e13613
+Bug: https://github.com/libexpat/libexpat/issues/532
+Forwarded: no
+Last-Update: 2022-05-27
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- libxmltok-1.2.orig/xmlparse/xmlparse.c
 libxmltok-1.2/xmlparse/xmlparse.c
+@@ -2616,9 +2616,14 @@ doProlog(XML_Parser parser,
+ #endif /* XML_DTD */
+ case XML_ROLE_GROUP_OPEN:
+   if (prologState.level >= groupSize) {
+-  if (groupSize)
++  if (groupSize) {
++/* Detect and prevent integer overflow */
++if (groupSize > (unsigned int)(-1) / 2u) {
++  return XML_ERROR_NO_MEMORY;
++}
++
+ groupConnector = realloc(groupConnector, groupSize *= 2);
+-  else
++  } else
+ groupConnector = malloc(groupSize = 32);
+   if (!groupConnector)
+ return XML_ERROR_NO_MEMORY;
diff -Nru libxmltok-1.2/debian/patches/series 
libxmltok-1.2/debian/patches/series
--- libxmltok-1.2/debian/patches/series 2017-08-10 08:53:42.0 -0300
+++ libxmltok-1.2/debian/patches/series 2022-05-30 16:58:54.0 -0300
@@ -1 +1,2 @@
 debian-changes.patch
+CVE-2021-46143.patch


Bug#993995: Acknowledgement (upgrade-reports: lost abilty to do fast repeated key strokes after upgrade from buster to bullseye)

2021-09-09 Thread J. Rodrigo Flores
SOLVED.

Took me 2.5 hours to find after the upgrade,
Going to Settings, accesibility, typing assists, disabling "ignores
fast duplicate keypresses "

best
Rodrigo

On 09/09/2021, Debian Bug Tracking System  wrote:
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 993995:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993995.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> As you requested using X-Debbugs-CC, your message was also forwarded to
>   rodrigo.flores...@gmail.com
> (after having been given a Bug report number, if it did not have one).
>
> Your message has been sent to the package maintainer(s):
>  Debian Testing Group 
>
> If you wish to submit further information on this problem, please
> send it to 993...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 993995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993995
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>


-- 

Rodrigo



Bug#992083: Mod tidy should ignore missing standard library packages (fixed in go >= 1.15.10)

2021-08-11 Thread Rodrigo Campos

Package: golang-1.15
Version: 1.15.9-6
Severity: normal

Hi!

I'm currently trying to run go mod tidy on runc master[1] 
(16027b814d59403b71bb369a0ba064da47dd302b) and fails with this error:


io/fs: package io/fs is not in GOROOT 
(/usr/lib/go-1.15/src/io/fs)

Googling a little bit about it, it seems this a bug in go that should 
ignore the package that were introduced in go 1.16 (it is properly 
guarded with build tags in the runc repo).


This comment on viper has pointers to the bugs in go upstream:
https://github.com/spf13/viper/issues/1161#issuecomment-869702237

This bugfix was backported to go 1.10[2] that was released in March 
2021[3]. It will be great if the fix can be included on debian packaged 
version.


Let me know if I can help in any way


Best,
Rodrigo

[1]: https://github.com/opencontainers/runc/
[2]: https://github.com/golang/go/issues/44792
[3]: https://golang.org/doc/devel/release#go1.15.minor



Bug#990820: DefaultErrnoRet not working with runc 1.0

2021-07-08 Thread Rodrigo Campos

On 7/8/21 5:57 PM, Shengjing Zhu wrote:

Hi,


Hi! :)



On Thu, Jul 8, 2021 at 7:12 PM Rodrigo Campos  wrote:

runc 1.0 from debian repositories doesn't honor DefaultErrnoRet, that


It's expected. As I disable that in
https://salsa.debian.org/go-team/packages/runc/-/blob/experimental/debian/patches/0010-compatible-with-specs-go-1.0.2.41.g7413a7f.patch


Ohh, it makes sense.


The reason behind is just simple.
golang-github-opencontainers-specs-dev in Debian unstable is just at
version 1.0.2.41.g7413a7f-1, which don't support DefaultErrnoRet.
I plan to update the spec package after bullseye release, which is
planned at July 31. But if you really want to use this feature before
that day, I may update the spec package in experimental first.


No, no need to update it now. Your plan is just fine for me :)

When you update the runtime-spec, it will be great if the version is in 
sync with what runc vendors. In particular, if it includes this PR I did 
to the runtime-spec 
(https://github.com/opencontainers/runtime-spec/pull/1074) it will be 
great (the version of the runtime-spec that runc 1.0 vendors already 
includes that :))



Thanks again and sorry for the silly report, didn't see the patch! :)


Best,
Rodrigo



Bug#982302: Outdated ghostscript font paths

2021-02-08 Thread Rodrigo Arias
Package: groff
Version: 1.22.4-3

When building a PDF with groff 1.22.4-3 [1] on Debian buster, it 
complains that some fonts are missing:

% groff -ms -k -t -p -R -Tpdf test.ms > test.pdf
test.ms: Failed to open '/usr/share/ghostscript/9.26/Resource/Font/P052-Bold'

The last version of ghostscript at current time is 9.27 with the fonts 
provided by the package libgs9-common [2], located at:

% ls -1 /usr/share/ghostscript/9.27/Resource/Font
C059-BdIta
C059-Bold
C059-Italic
C059-Roman
D05L
NimbusMonoPS-Bold
NimbusMonoPS-BoldItalic
NimbusMonoPS-Italic
NimbusMonoPS-Regular
NimbusRoman-Bold
...

While in groff, the paths are outdated as they point to the 9.26 
version:

% awk '/ghost/{print $2}' /usr/share/groff/1.22.4/font/devpdf/download
/usr/share/ghostscript/9.26/Resource/Font/URWGothic-Book
/usr/share/ghostscript/9.26/Resource/Font/URWGothic-BookOblique
/usr/share/ghostscript/9.26/Resource/Font/URWGothic-Demi
/usr/share/ghostscript/9.26/Resource/Font/URWGothic-DemiOblique
/usr/share/ghostscript/9.26/Resource/Font/URWBookman-Demi
/usr/share/ghostscript/9.26/Resource/Font/URWBookman-DemiItalic
/usr/share/ghostscript/9.26/Resource/Font/URWBookman-LightItalic
/usr/share/ghostscript/9.26/Resource/Font/URWBookman-Light
*/usr/share/ghostscript/9.26/Resource/Font/NimbusMonoPS-Regular
*/usr/share/ghostscript/9.26/Resource/Font/NimbusMonoPS-Bold
...

It seems that the paths in the "download" file are generated at build 
time pointing to the ghostscript installation, detected in the configure 
phase [3,4]. Therefore, rebuilding groff again should be enough to fix 
the paths.

Rodrigo.

[1]:https://packages.debian.org/buster/groff
[2]:https://packages.debian.org/buster/all/libgs9-common/filelist
[3]:https://git.savannah.gnu.org/cgit/groff.git/tree/font/devpdf/devpdf.am
[4]:https://git.savannah.gnu.org/cgit/groff.git/tree/font/devpdf/util/BuildFoundries.pl

http://bsc.es/disclaimer



Bug#982055: O: dia -- Diagram editor

2021-02-05 Thread Rodrigo Carvalho
Package: wnpp
Severity: normal

I intend to orphan the dia package.

The package description is:
 Dia is an editor for diagrams, graphs, charts etc. There is support for UML
 static structure diagrams (class diagrams), Entity-Relationship diagrams,
 network diagrams and much more. Diagrams can be exported to postscript and
 many other formats.



Bug#966676: O: vtun -- virtual tunnel over TCP/IP networks

2020-08-01 Thread Rodrigo Carvalho
Package: wnpp
Severity: normal

I intend to orphan the vtun package.

The package description is:
 VTun is the easiest way to create virtual tunnels over TCP/IP networks
 with traffic shaping and compression.
 .
 It supports IP, PPP, SLIP, Ethernet and other tunnel types.
 .
 VTun is easily and highly configurable, it can be used for various
 network tasks.
 .
 VTun requires the universal TUN/TAP kernel module which can be found at
 http://vtun.sourceforge.net/tun/index.html or in the 2.4 and newer Linux
 kernels.
 .
 Note: This program includes an "encryption" feature intended to protect the
 tunneled data as it travels across the network. However, the protocol it uses
 is known to be very insecure, and you should not rely on it to deter anyone
 but a casual eavesdropper. See the included README.Encryption file for more
 information.



Bug#961835: ITP: r-cran-ecosolver -- Embedded Conic Solver in R

2020-05-29 Thread Rodrigo Carvalho
Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-ecosolver -- Embedded Conic Solver in R
Package: wnpp
Owner: Rodrigo Carvalho 
Severity: wishlist

* Package name: r-cran-ecosolver
  Version : 0.5.3
  Upstream Author : Anqi Fu,
* URL : https://cran.r-project.org/package=ECOSolveR
* License : GPL-3+
  Programming Lang: GNU R
  Description : Embedded Conic Solver in R
 R interface to the Embedded COnic Solver (ECOS), an efficient
 and robust C library for convex problems. Conic and equality
 constraints can be specified in addition to integer and
 boolean variable constraints for mixed-integer problems. This
 R interface is inspired by the python interface and has
 similar calling conventions.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-ecosolver



Bug#961693: ITP: r-cran-gmp -- Multiple Precision Arithmetic

2020-05-27 Thread Rodrigo Carvalho
Package: wnpp
Severity: wishlist
Owner: Rodrigo Carvalho 

* Package name: r-cran-gmp
  Version : 0.5-14
  Upstream Author : Antoine Lucas, Immanuel Scholz, Rainer Boehme,
Sylvain Jasson, Martin Maechler
* URL : https://cran.r-project.org/package=gmp
* License : GPL-2 | GPL-3
  Programming Lang: R and C++
  Description : Multiple Precision Arithmetic

Multiple Precision Arithmetic (big integers and rationals,
 prime number tests, matrix computation), "arithmetic without limitations"
 using the C library GMP (GNU Multiple Precision Arithmetic).

It will be maintained by R Packages Team



Bug#950150:

2020-03-25 Thread Rodrigo Aguilera
I experiencing this under debian testing on wayland (audacity 2.3.3).

Seems to be wayland related. Changing the session to Xorg solves the
problem.

I am reporting this to the developers here
https://github.com/audacity/audacity/issues/471


Bug#926202: Seems this can be closed

2020-03-25 Thread Rodrigo Campos
IMHO, this can be closed as the fix (I've verified with a repro) is
included now. But maybe can you, jaros...@thinline.cz, try to
reproduced with those kernels I mentioned and report back?



Bug#926202: Fixed upstream

2020-03-25 Thread Rodrigo Campos
tags 926202 + fixed-upstream

We (at Kinvolk) hit the very same bug (fault_state(0x5862)!) and
created a way to reproduce with fio to have heavy IO. All the info is
here: https://github.com/flatcar-linux/Flatcar/issues/12

As it's shown in the link, this was fixed in
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=9e034c61951acdc1378d936875641fcb61b6a7a3
and 4.19.65 is the first stable release to include it. Also, note
there are more fixes in later stable release, but our repro doesn't
hit this as of 4.19.65

The bug you reference in Ubuntu is similar but is not the same, IIUC.
The fault state hex code returned there is different (not 0x5862), so
this probably indicates a different controller error.

Debian linux-image-4.19.0-6-amd64 seems to incoporate this commit/fix
in version 4.19.67-1. In backports (I see the report is for
backports), this seems to be fixed in linux-image-4.19.0-0.bpo.6-amd64
version 4.19.67-2~bpo9+1.


Hope this helps



Bug#951809: nmu: kworkflow_20191112-1

2020-02-21 Thread Rodrigo Carvalho
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Hello,

something gone wrong when rebuild on amd64 after sponsorship. So please
build it on that arch.

  nmu kworkflow_20191112-1 . amd64 . unstable . -m "build on amd64
after a failure"

Thanks



Bug#951676: RFS: dia/0.97.3+git20160930-9 -- Diagram editor

2020-02-19 Thread Rodrigo Carvalho
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "dia"

 * Package name: dia
   Version : 0.97.3+git20160930-9
   Upstream Author : several authors
 * URL : https://wiki.gnome.org/Apps/Dia/
 * License : GPL-2
 * Vcs : None
   Section : graphics

It builds those binary packages:

  dia-common - Diagram editor (common files)
  dia - Diagram editor

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/dia

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/d/dia/dia_0.97.3+git20160930-9.dsc

Changes since the last upload:

   * New maintainer.
   * Disable use of xml_config. Now we use pkg_config. (Closes: #949097).
   * debian/rules: remove unnecessary dh argument
   * debian/control:
 - remove obsolete VCS URLs (anonscm no longer exists,
   we should create a VCS on salsa).
 - Standards-Version: 4.5.0.

OBS: There is a maintainer swap. Rodrigo Siqueira have already agreed.
CC Siqueira who can
confirm, if necessary.

Regards,

--
  Rodrigo Carvalho



Bug#947452: RFS: kworkflow/20191112-1 [ITP] -- Inglorious kernel developer workflow scripts

2020-01-21 Thread Rodrigo Carvalho
A new version was uploaded. Thanks Adam!



Bug#947452: RFS: kworkflow/20191112-1 [ITP] -- Inglorious kernel developer workflow scripts

2019-12-28 Thread Rodrigo Carvalho
Hi Adam!

Em sex., 27 de dez. de 2019 às 19:17, Adam Borowski
 escreveu:
>
> On Fri, Dec 27, 2019 at 01:12:26AM -0300, Rodrigo Carvalho wrote:
> >  * Package name: kworkflow
> >Version : 20191112-1
>
> > Changes since the last upload:
> >
> >* Initial release. Closes: #946781
>
> Hi!
> I'm afraid that autopkgtest fails, as it tries to access the current user's
> $HOME.  No package should reach outside of its build dir, during either the
> compile or test step.
>
> You can eg. set $HOME to $AUTOPKGTEST_TMP which is a valid writeable dir.

Thanks for the tip. I uploaded a new version. I hope now it works fine.

>
> autopkgtest [23:13:22]: test kw-basic-test: [---
> error: could not lock config file /home/kilobyte/.gitconfig: No such file or 
> directory
> error: could not lock config file /home/kilobyte/.gitconfig: No such file or 
> directory
> Running test [checkpatch_wrapper_test]
> =
> testWarning
> testError
> testChecks
> testCorrect
>
> Ran 4 tests.
>
> OK
> Running test [commons_test]
> =
> testParseRegularConfig
> testParseUnsupportedFile
> testDefaultConfigFile
> testLocalConfigFile
>
> Ran 4 tests.
>
> OK
> Running test [configm_test]
> =
> testExecuteConfigManagerSAVEfails
> testSaveConfigFileCHECK_CONFIGfails
> testSaveConfigFileCHECK_CONFIGS_DIRECTORY
> testSaveConfigFileCHECK_SAVED_CONFIG_FILE
> testSaveConfigFileCHECK_DESCRIPTION
> testSaveConfigFileCHECK_GIT_SAVE_SCHEMA
> testSaveConfigFileCHECK_FORCE
> testListConfigsCHECK_NO_CONFIGS
> testListConfigsOUTPUT
> testGetOperationWithForce
> testGetOperationThatShouldFail
> testRemoveOperationThatShouldFail
> testRemoveOperation
>
> Ran 13 tests.
>
> OK
> Running test [explore_test]
> =
> testExplore
>
> Ran 1 test.
>
> OK
> Running test [fish_completion_test]
> =
> testKwCompletion
>
> Ran 1 test.
>
> OK
> Running test [get_maintainer_wrapper_test]
> =
> testPrintFileAuthorForFile
> testPrintFileAuthorForDir
> testGetMaintainers
>
> Ran 3 tests.
>
> OK
> Running test [help_test]
> =
> testHelp
>
> Ran 1 test.
>
> OK
> Running test [kw_dash]
> =
> testDash
> install: cannot create directory ‘/home/kilobyte’: Permission denied
> cp: cannot create directory '/home/kilobyte/.config/kw': No such file or 
> directory
> sed: can't read /home/kilobyte/.config/kw/kworkflow.config: No such file or 
> directory
>
> Ran 1 test.
>
> OK
> Running test [kw_test]
> =
> install: cannot create directory ‘/home/kilobyte’: Permission denied
> cp: cannot stat '/tmp/autopkgtest.gQu1DL/build.mAh/src/tests/etc/.': No such 
> file or directory
> sed: can't read /home/kilobyte/.config/kw/kworkflow.config: No such file or 
> directory
> testVariables
> testExported
>
> Ran 2 tests.
>
> OK
> Running test [kwio_test]
> =
> testAlertOptions
> testAlertDefaultOptions
> testAlertCommandPrinting
>
> Ran 3 tests.
>
> OK
> Running test [kwlib_test]
> =
> linuxRootCheckTest
> cmdManagerTESTMODETest
> cmdManagerSILENTTest
> cmdManagerSAY_COMPLAIN_WARNING_SUCCESS_Test
> detectDistroTest
> joinPathTest
> findKernelRootTest
> isAPatchTest
>
> Ran 8 tests.
>
> OK
> Running test [ssh_test]
> =
> vmSshFailsTest
> vmSshTest
> vmSshCommandTest
> vmSshScriptTest
>
> Ran 4 tests.
>
> OK
> =
> Total: 12 test file(s)
> Test file(s) SUCCEEDED
> test_codestyle
> install: cannot create directory ‘/home/kilobyte’: Permission denied
> cp: cannot create directory '/home/kilobyte/.config/kw': No such file or 
> directory
> sed: can't read /home/kilobyte/.config/kw/kworkflow.config: No such file or 
> directory
> test_maintainers
> install: cannot create directory ‘/home/kilobyte’: Permission denied
> cp: cannot create directory '/home/kilobyte/.config/kw': No such file or 
> directory
> sed: can't read /home/kilobyte/.config/kw/kworkflow.config: No such 

Bug#947452: RFS: kworkflow/20191112-1 [ITP] -- Inglorious kernel developer workflow scripts

2019-12-26 Thread Rodrigo Carvalho
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "kworkflow"

 * Package name: kworkflow
   Version : 20191112-1
   Upstream Author : Rodrigo Siqueira 
 * URL : https://github.com/kworkflow/kworkflow
 * License : GPL-2+
 * Vcs : https://github.com/kworkflow/kworkflow
   Section : misc

It builds those binary packages:

  kworkflow - Inglorious kernel developer workflow scripts

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/kworkflow

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/k/kworkflow/kworkflow_20191112-1.dsc

Changes since the last upload:

   * Initial release. Closes: #946781

Regards,

--
  Rodrigo Carvalho



Bug#946781: ITP: kw -- Inglorious kernel developer workflow scripts

2019-12-15 Thread Rodrigo Carvalho
Package: wnpp
Severity: wishlist
Owner: Rodrigo Carvalho 

* Package name: kw
  Version : 20191112
  Upstream Author : Rodrigo Siqueira 
* URL : https://github.com/kworkflow/kworkflow
* License : GPL-2
  Programming Lang: Shell Script
  Description : Inglorious kernel developer workflow scripts

kw is a set of scripts that
have mission to reduce the overhead
related with infrastructure project setup in
projects that have a similar workflow to the Linux Kernel.

kw stands for Kernel Workflow.



Bug#944508: RFS: vtun/3.0.4-2 -- virtual tunnel over TCP/IP networks

2019-11-10 Thread Rodrigo Carvalho
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "vtun"

 * Package name: vtun
   Version : 3.0.4-2
   Upstream Author : Maxim Krasnyansky 
 * URL : http://vtun.sourceforge.net/
 * License : GPL-2+
 * Vcs : None
   Section : net

It builds those binary packages:

  vtun - virtual tunnel over TCP/IP networks

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/vtun

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/v/vtun/vtun_3.0.4-2.dsc

Changes since the last upload:

   * Fix HAVE_WORKING_FORK configure check. Patch by Sylvain Rochet.
 (Closes: #943436).

Regards,

--
  Rodrigo Carvalho



Bug#944429: rdiff-backup: Update upstream homepage in project profile

2019-11-09 Thread Rodrigo Silva
Package: rdiff-backup
Version: 1.2.8-7
Severity: minor

https://tracker.debian.org/pkg/rdiff-backup shows Upstream Homepage as
http://rdiff-backup.nongnu.org/ , but project moved from Savanah to Github a
while ago.

New upstream homepage:
https://rdiff-backup.net/

Repository:
https://github.com/rdiff-backup/rdiff-backup



-- System Information:
Debian Release: buster/sid
  APT prefers bionic-updates
  APT policy: (500, 'bionic-updates'), (500, 'bionic-security'), (500, 
'bionic'), (100, 'bionic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-66-generic (SMP w/12 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages rdiff-backup depends on:
ii  libc6  2.27-3ubuntu1
ii  librsync1  0.9.7-10build1
ii  python 2.7.15~rc1-1
ii  python2.7  2.7.15-4ubuntu4~18.04.2

Versions of packages rdiff-backup recommends:
ii  python-pylibacl  0.5.3-1build2
ii  python-pyxattr   0.6.0-2build2

rdiff-backup suggests no packages.

-- no debconf information



Bug#936086: RFS: vtun/3.0.4-1 [ITA] -- virtual tunnel over TCP/IP networks

2019-08-29 Thread Rodrigo Carvalho
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "vtun"

 * Package name: vtun
   Version : 3.0.4-1
   Upstream Author : Maxim Krasnyansky 
 * URL : http://vtun.sourceforge.net/
 * License : GPL-2+
 * Vcs : None
   Section : net

It builds those binary packages:

  vtun - virtual tunnel over TCP/IP networks

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/vtun

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/v/vtun/vtun_3.0.4-1.dsc

Changes since the last upload:

   * New upstream release.
   * New maintainer (Closes: #812758).
   * debian/rules: use of dpkg-buildflags instead of obsolete finding for
 noopt in DEB_BUILD_OPTIONS.
   * No stripping on building package. Patch by Helmut Grohne.
 (Closes: #883530).

Regards,

--
  Rodrigo Carvalho



Bug#935113: ITA: vtun -- virtual tunnel over TCP/IP networks

2019-08-19 Thread Rodrigo Carvalho
Package: wnpp
Severity: normal

I intend to adopt the vtun package.

The package description is:
 VTun is the easiest way to create virtual tunnels over TCP/IP networks
 with traffic shaping and compression.
 .
 It supports IP, PPP, SLIP, Ethernet and other tunnel types.
 .
 VTun is easily and highly configurable, it can be used for various
 network tasks.
 .
 VTun requires the universal TUN/TAP kernel module which can be found at
 http://vtun.sourceforge.net/tun/index.html or in the 2.4 and newer Linux
 kernels.
 .
 Note: This program includes an "encryption" feature intended to protect the
 tunneled data as it travels across the network. However, the protocol it uses
 is known to be very insecure, and you should not rely on it to deter anyone
 but a casual eavesdropper. See the included README.Encryption file for more
 information.



Bug#931961: onboard not work

2019-07-12 Thread Rodrigo Lima de Souto Leandro
Package: onboard
Version: 1.4.1-4+b1
Severity: grave
Tags: a11y
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
when I open the gnome terminal it opens and closes the onboard and standard
gnome keyboard, non-stop
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
open the terminal
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



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

Kernel: Linux 5.2.0-elm (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages onboard depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1
ii  gir1.2-glib-2.0  1.58.3-2
ii  gir1.2-gtk-3.0   3.24.5-1
ii  gir1.2-pango-1.0 1.42.4-6
ii  iso-codes4.2-1
ii  libc62.28-10
ii  libcairo-gobject21.16.0-4
ii  libcairo21.16.0-4
ii  libcanberra0 0.30-7
ii  libdconf10.30.1-2
ii  libgcc1  1:8.3.0-6
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-2
ii  libgtk-3-0   3.24.5-1
ii  libhunspell-1.7-01.7.0-2
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  librsvg2-common  2.44.10-2.1
ii  libstdc++6   8.3.0-6
ii  libudev1 241-5
ii  libx11-6 2:1.6.7-1
ii  libxi6   2:1.7.9-1
ii  libxkbfile1  1:1.0.9-2+b11
ii  libxtst6 2:1.2.3-1
ii  onboard-common   1.4.1-4
ii  python3  3.7.3-1
ii  python3-cairo1.16.2-1+b1
ii  python3-dbus 1.2.8-3
ii  python3-gi-cairo 3.30.4-1

Versions of packages onboard recommends:
ii  gir1.2-atspi-2.0 2.30.0-7
ii  gir1.2-ayatanaappindicator3-0.1  0.5.3-4
ii  onboard-data 1.4.1-4
ii  xdg-utils1.1.3-1

Versions of packages onboard suggests:
ii  mousetweaks  3.12.0-5

-- no debconf information



Bug#929085: thunar: Thunar and firefox crshe in the xorg, make it freeze the display.

2019-05-16 Thread Rodrigo Lima de Souto Leandro
Package: thunar
Version: 1.8.4-1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Open the app, thunar, firefox and others
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Only open the apps.
   * What was the outcome of this action?
Open the apps but I correct when Restart the lightdm or ctrl+alt+f2 and 
return for X with alt+f7 that the X show next display freeze.
   * What outcome did you expect instead?

My notebook is Acer Aspire A515-41G-1480 (AMD A12, Radeon RX 540 and memory 
DDR4)

*** End of the template - remove these template lines ***


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

Kernel: Linux 4.19.0-4-rt-amd64 (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages thunar depends on:
ii  desktop-file-utils  0.23-4
ii  exo-utils   0.12.4-1
ii  libatk1.0-0 2.30.0-2
ii  libc6   2.28-10
ii  libcairo2   1.16.0-4
ii  libexo-2-0  0.12.4-1
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libglib2.0-02.58.3-1
ii  libgtk-3-0  3.24.5-1
ii  libgudev-1.0-0  232-2
ii  libice6 2:1.0.9-2
ii  libnotify4  0.7.7-4
ii  libpango-1.0-0  1.42.4-6
ii  libsm6  2:1.2.3-1
ii  libthunarx-3-0  1.8.4-1
ii  libxfce4ui-2-0  4.12.1-3
ii  libxfce4util7   4.12.1-3
ii  libxfconf-0-2   4.12.1-1
ii  shared-mime-info1.10-1
ii  thunar-data 1.8.4-1

Versions of packages thunar recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.12.12-1
ii  dbus-x11 [dbus-session-bus]   1.12.12-1
ii  gvfs  1.38.1-3
ii  libcairo-gobject2 1.16.0-4
ii  libpangocairo-1.0-0   1.42.4-6
ii  libxfce4panel-2.0-4   4.12.2-1
ii  policykit-1-gnome [polkit-1-auth-agent]   0.105-7
ii  thunar-volman 0.9.1-1
ii  tumbler   0.2.3-1
ii  udisks2   2.8.1-4
ii  xdg-user-dirs 0.17-2

Versions of packages thunar suggests:
ii  thunar-archive-plugin 0.4.0-2
ii  thunar-media-tags-plugin  0.3.0-2

-- no debconf information



Bug#926926: [Intel-gfx] Bug#926926: thinkpad_acpi: Unable to use VGA port on Lenovo Docking station after boot

2019-04-15 Thread Rodrigo Vivi
Hi Mario,

Could you please file a bugzilla entry following
https://01.org/linuxgraphics/documentation/how-report-bugs
?

Do you recall what kernel version you had before Apr-10?

Thanks,
Rodrigo.

On Fri, Apr 12, 2019 at 10:22:53AM +, ^-¨ Mário Lopes wrote:
> Package: linux-image-4.19.0-0.bpo.4-amd64
> Version: 4.19.28-2~bpo9+1
> X-Debbugs-CC: ibm-a...@hmh.eng.br, ibm-acpi-de...@lists.sourceforge.net, 
> platform-driver-...@vger.kernel.org, intel-...@lists.freedesktop.org
> 
> Dear Maintainer,
> 
> I have a Lenovo ThinkPad T480s with Intel GFX and a Lenovo ThinkPad Ultra 
> Docking Station.
> I'm using an LG monitor connected to Display Port of docking station, at 
> 1080p@60Hz, configured as primary monitor.
> I'm also using a HannStar monitor, connected to VGA port of docking station, 
> at 1280x1024@75Hz, configured as secondary monitor.
> The built-in T480s screen is also active, at 2K, configured as secondary 
> monitor.
> 
> Since updates available at 10/April, I need to reconnect the VGA cable to use 
> the monitor after cold start. Sometimes, it's also needed to reboot the 
> laptop.
> The same also happens when I lock the computer, only when monitors enter in 
> suspend mode and when I got into lock screen, the VGA monitor doesn't receive 
> any signal, so VGA reconnection or system reboot is needed. The workaround 
> for this is just to lock without sending suspending commands to monitors.
> 
> I didn't saw any relevant information on dmesg output, but I can provide 
> relevant info from this or other place if needed.
> 
> Before 10/April, it was only needed to reconnect VGA, let's say, one per week.
> 
> Thanks.
> 
> 
> Best regards,
> Mário J. Lopes
> ___
> Intel-gfx mailing list
> intel-...@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx



Bug#887600: Bug#887602: Your package FTBFS with freetype 2.9.1

2018-10-29 Thread Rodrigo Siqueira
Hi,

First of all, sorry for the delay.

I will work in this bug this week and report new as soon as possible.

Thanks a lot for the report

On 10/19, Hugh McMaster wrote:
> Control: severity -1 serious
> 
> Dear maintainer,
> 
> Freetype 2.9.1-2 has been in experimental for three weeks now. As it is 
> working well, I have decided to upload the package to unstable within the 
> next two to three weeks.
> 
> A rebuild of your package with freetype 2.9.1 installed confirmed that your 
> package will FTBFS once the new version of freetype enters unstable. In 
> almost all cases, this build failure was caused by the configure script not 
> detecting the freetype libraries, as freetype-config is not shipped in 2.9.1.
> 
> Given the build failure and upcoming upload of freetype 2.9.1, I am raising 
> the severity of this bug to Serious.
> 
> Please use pkg-config to detect freetype.
> 
> Thank you

-- 
Rodrigo Siqueira
https://siqueira.tech
https://twitter.com/siqueirajordao
Graduate Student
Department of Computer Science
University of São Paulo


signature.asc
Description: PGP signature


Bug#884887: chromium: rejects access to microphone without prompt

2018-09-26 Thread Rodrigo Aguilera
This is really annoying. Please fix it.

Take into account that you also need to have chromium turned off before
editing the preferences file so it doesn't get overwritten.


Bug#881564: A64-OLinuXino

2018-09-14 Thread Rodrigo Exterckötter Tjäder
I built the version of the package on experimental with the patch on
message #10.

Then I installed it and the ATF from atf-allwinner package to a SD
card using "TARGET=/usr/lib/u-boot/a64-olinuxino
u-boot-install-sunxi64 /dev/mmcblk1".

With that SD card on the board I got an U-Boot prompt and managed to
boot into debian-installer using the daily kernel and initrd.

>From that prompt I also managed to boot the Ubuntu installation on the
internal eMMC, and everything seemed to work there.

On the U-Boot prompt neither ethernet nor USB work:

> => dhcp
> No ethernet found.
> => usb start
> starting USB...
> No controllers found

All of this was tested over the serial port, I haven't tested the HDMI
output, nor do I know if it is expected to work.

Even though USB and ethernet are not working I would say the image is
useful enough that it should be included.



Bug#881564: A64-OLinuXino

2018-09-12 Thread Rodrigo Exterckötter Tjäder
On Wed, Sep 12, 2018 at 6:26 PM, Vagrant Cascadian  wrote:
> It's more than just a one-time test needed; someone needs to be willing
> to test new versions periodically, so we don't end up with an unusable
> u-boot installed on someone's machine in a stable release.
>
> For more information about being a tester, please see:
>
>   https://wiki.debian.org/U-boot
>   https://wiki.debian.org/U-boot/Status
>
> Most important is to run the tests with the default u-boot environment,
> otherwise you can end up with bugs leftover from older versions. For
> this reason, I avoid using saveenv from the u-boot prompt. Ideally also
> testing both a cold boot as well as reboot, and if possible various boot
> methods. You would also kind of serve as a point of contact to help
> troubleshoot issues with u-boot.

I don't have much experience with u-boot, but I'm willing to learn and
test new versions.

> If you're up for doing that and having your name and email in the
> debian/targets file listed with whatever board(s) you're willing to
> test, reply to the bug and I'll add it to the next upload!

Sure, no problem.



Bug#881564: A64-OLinuXino

2018-09-12 Thread Rodrigo Exterckötter Tjäder
Hello,

I just got an A64-OLinuXino and would like to get Debian working on
it. It seems to be that getting u-boot-sunxi to ship a version for
this board is the first step.

It seems this bug is on hold because there is no one available to test
it. Is there anything I can do to help with that?



Bug#100808: Business Partnership Request

2018-07-12 Thread Rodrigo Romero Tasiguano


Hello,
I am seeking your consent for a prospective and risk free business 
collaboration, Contact my private email for more details. Email:  
h@outlook.com
Thanks,



Bug#902876: wordpress: CVE-2018-12895

2018-07-09 Thread Rodrigo Campos
On Mon, Jul 09, 2018 at 10:04:56PM +1000, Craig Small wrote:
> I have sent the debdiff for stretch to the security team. Once they are
> happy about it, stretch will get that update.

Great, thanks a lot! :-)



Bug#902876: wordpress: CVE-2018-12895

2018-07-07 Thread Rodrigo Campos
On Sat, Jul 07, 2018 at 10:35:44PM +1000, Craig Small wrote:
> Looks like they made a release, 4.9.7 with the fix. Uploading soon.
> 
> The relevant patch (for backports) is
> https://github.com/WordPress/WordPress/commit/c9dce0606b0d7e6f494d4abe7b193ac046a322cd

I can only backport from packages in stable, so we need it applied there first 
:-)



Bug#900060: apt-get build-dep debian-policy installs too much

2018-05-27 Thread Rodrigo Siqueira
On 05/25, Sean Whitton wrote:
> control: reassign -1 dia
> control: severity -1 wishlist
> control: retitle -1 Provide binary package containing CLI dia, without GUI 
> dependencies
> 
> Hello,
> 
> On Fri, May 25 2018, Russ Allbery wrote:
> 
> > dia is at fault for all of this, which is in Build-Depends to allow
> > the maintainer script state diagrams to be maintained in the preferred
> > form for modification.
> >
> > It depends on python-gtk2, which in turn depends on python-numpy.  It
> > also depends on libgtk2.0-0, which depends on libcups2, which pulls in
> > libavahi-common3.  libgtk2.0-0 depends on both gnome-icon-theme and
> > hicolor-icon-theme (but gnome-icon-theme depends on hicolor-icon-theme
> > anyway).
> 
> On Fri, May 25 2018, Russ Allbery wrote:
> 
> > Ian Jackson  writes:
> >
> >> I'm afraid to ask, but: why does python-gtk2 depend on numpy ?  Don't
> >> get me wrong, I like numpy, but, err, needed for gtk ?
> >
> >> Also, does dia really need python-gtk2 for the invocations we are
> >> using ?  Or, indeed for most of its invocations ?  ... looks at the
> >> manpage ... oh it's primarily a gui program.  *sigh*
> >
> > Yeah, it's a GUI program we're running in batch mode.  In an ideal
> > world, there would be some separate library and CLI tool that would do
> > batch conversions that would be kept separate from all the GUI
> > machinery, but I'm sure life is short for upstream and they haven't
> > had an obvious reason to bother with this.
> 
> Ah.
> 
> Reassigning, as the bug is not in the debian-policy package.  Hopefully
> I've quoted enough context for the dia maintainer (who is CCed).

Hi,

I will carefully look at the issues pointed out in the thread.

Thanks for the report.
 
> -- 
> Sean Whitton



Bug#892910: libsundials-serial-dev: Fails to link when making shared object using these libs

2018-03-14 Thread Rodrigo
Package: libsundials-serial-dev
Version: 2.5.0-3+b3
Severity: important

Dear Maintainer,

Trying to compile against the libs shows the following error:

/usr/bin/ld: /usr/lib/libsundials_fkinsol.a(fkinsol.o): relocation R_X86_64_32
against symbol `FKINfunc' can not be used when making a shared object;
recompile con -fPIC

Recompiling with -fPIC solves the issue.



-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages libsundials-serial-dev depends on:
ii  libblas-dev 3.7.0-2
ii  liblapack-dev   3.7.0-2
ii  libsundials-serial  2.5.0-3+b3

libsundials-serial-dev recommends no packages.

libsundials-serial-dev suggests no packages.

-- no debconf information



Bug#892010: exo-utils: exo-preferred-applications does not run with error "exo-helper-1: not found"

2018-03-03 Thread Rodrigo Campos
Package: exo-utils
Version: 0.12.0-1
Severity: normal

Dear Maintainer,

When running "exo-preferred-applications" it fails with:

/usr/bin/exo-preferred-applications: 11: exec: 
/usr/lib/x86_64-linux-gnu/xfce4/exo-1/exo-helper-1: not found

The exo-preferred-applications seems to be a shell script that runs that:

$ cat /usr/bin/exo-preferred-applications
#!/bin/sh
#
#
# Copyright (c) 2005-2006 Benedikt Meurer <be...@xfce.org>
#
# Opens the "Preferred Applications" dialog, which
# allows users to configure their preferred Web
# Browser, Mail Reader and Terminal Emulator.
#

exec /usr/lib/x86_64-linux-gnu/xfce4/exo-1/exo-helper-1 --configure "$@"

That file is installed with libexo-1-0, although this exo-utils version (as the
package description says) should use libexo-2-0, IIUC.

The package properly depends on libexo-2-0 but my guess is that the script 
needs some
update?

I've manually installed libexo-1-0 and that did the trick for running
exo-preferred-applications. It seems xfce is using those configurations too, so
seems fine as a work-around :)


Please let me know if I can help with testing or something



Thanks a lot,
Rodrigo



Bug#838537: sponsoring Dia package

2018-02-05 Thread Rodrigo Siqueira
Hello Tomas,
 
> Are you still willing to adopt the package? I'd be ready to sponsor you.

Yes :)
Should we change the status of the package?

> As a first step I'd suggest to send your patches upstream [1], so that they
> can be applied there.

Nice! I will read the documentation about send patches to Dia project, and try
to upload the patches. I will let you know when I finish it.

Again, Thanks :)



Bug#885641: RFS: xml-core/0.18-1 [ITA]

2017-12-29 Thread Rodrigo Siqueira
> > Xml-core itself needs a rewrite especially to separate the catalogs per
> > apps, add tests etc.
> > There was a RFH about it a few years back FYI.
> 
> Exactly, see #660687 which was the original RFH.
> Nowadays there is only one open bug report which could really do with a
> fix for example.
> 
> Also, Even if it is really orphaned I'd still recommend to keep it
> within the xml-sgml team (CCed, who knows, somebody might actually
> reply…), so the steps IMHO would be
> 1) clone the git repo
> 2) `gbp import-dch` the last upload from Eriberto which wasn't imported
> yet (which tbh I don't understand why it happened, it's rare to do an
> upload with the only interesting delta being the change in maintainer)
> 3) do stuff there
> 4) get somebody from the team review and upload
> 
> Sure, nothing stops you from maintaining it on your own (which makes me
> notice, you didn't remove/changed the Vcs-* fields in the changelog you
> showed in the first message, which should be done as you can't push to
> the repo in the xml-sgml team).

I will look at the steps described above and the issue. I will rework on the
package based on the steps described above, thanks.



Bug#885641: RFS: xml-core/0.18-1 [ITA]

2017-12-28 Thread Rodrigo Siqueira
Hi, thanks for your questions. :)

I will reply your questions, in the reverse order.

> This is a native package, so really "Adopting" it also means taking care
> of the (little) code there is inside.  Therefore, turning it into a 3.0
> (quilt) package is most probably not an appropriate action.

Change native to quilt probably was a mistake due to my lack of
experience. Thanks for pointing it out, I will read more for better
understand the difference between quilt and native.

> You wrote to the O bug, but without turning it into an ITA [...]

hummm...  Another mistake due to the lack of experience. I thought that
reply with the ITA in the subject changes it, sorry. My mistake. Could
you give me some hints here?

> [...] importantly without writing *why* you'd like to adopt such odd package.
> I'm honestly curious: I'm kind of biased here as I was the one massaging
> it into shape when it needed it last year.

I will try to be brief with my 'why'.

First of all, I am interested in software distribution and I really like
to understand about Debian package structure.

My first contact with xml-core came from my attempt to adopt dia
package, wherein the field "Depends on packages which need a new
maintainer" pointed out some packages, one of them is xml-core. I
decided to better understand xml-core. In the end, it sounds to me a
good opportunity to learn more about a native package and at the same
time reduce one of the dependencies without a maintainer (I am totally
aware about the responsibility to maintain a package). 
 
> And all in all, I personally doubt the usefulness of doing an upload
> only bumping std-ver (to a version that is not even the last) and just
> tweaking a couple of other fields.

I did what my current knowledge in Debian package enabled me to do. When
I looked at the xml-core files, I did not find anything that I can
improve, however, if there is any problem with it I will be glad to put
effort to improve it.



Bug#885641: RFS: xml-core/0.18-1 [ITA]

2017-12-28 Thread Rodrigo Siqueira
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "xml-core"

 Package name: xml-core
 Version : 0.18-1
 Upstream Author : Debian XML/SGML Group maintains
 URL : https://debian-xml-sgml.alioth.debian.org/
 License : GPL-2+
 Section : text

It builds those binary packages:

  xml-core   - XML infrastructure and XML catalog file support

To access further information about this package, please visit the following 
URL:

https://mentors.debian.net/package/xml-core


Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/x/xml-core/xml-core_0.18-1.dsc

Changes since the last upload:

  * New maintainer (Closes: #660687)
  * debian/control: bumped Standards-Version to 4.1.2
  * debian/control: bumped debhelper to 10 
  * debian/control: Added homepage
  * debian/source/format: update to use quilt

Regards,
 Rodrigo Siqueira



Bug#660687: ITA: xml-core

2017-12-19 Thread Rodrigo Siqueira
Hi,

I want to adopt xml-core. I already updated the package as can be seen attached,
and follows the changelog:

* New maintainer (Closes: #660687)
* debian/control: bumped Standards-Version to 4.1.2
* debian/control: bumped debhelper to 10 
* debian/source/format: update to use quilt

Thanks


xml-core_debian.tar.gz
Description: application/gzip


Bug#838633: ITA: dia-shapes

2017-12-19 Thread Rodrigo Siqueira
Hi,

I want to adopt dia-shapes. I already have a new version of the package
(attached).

Thanks


dia_shapes_debian.tar.gz
Description: application/gzip


Bug#838537: [ITA] Dia

2017-12-19 Thread Rodrigo Siqueira
Hi,

I want to adopt Dia package. I already updated the package and attached it in
this email. Follows the changelog:

* New maintainer (closes: #838537)
* debian/control: Bumped Standards-Version to 4.1.2
* debian/control: Bumped debhelper to 10
* debian/patches: Added a patch to fix typos
* debian/rules: Remove empty directories
* debian/rules: Added extra flags

I am ready to adopt it, I just need someone to sponsor me.

Thanks


dia_debian.tar.gz
Description: application/gzip


Bug#879934: pdfrw: please upgrade to 0.4 (needed for Python 3.X)

2017-10-27 Thread Rodrigo Siqueira Jordão

Hi,

I already updated it, I am waiting for my sponsor finish the review.

Quoting Piotr Ożarowski <pi...@sar0.p1otr.com>:


Source: pdfrw
Version: 0.3-1
Severity: normal

Dear Maintainer,

Please upgrade pdfrw to 0.4 as previous version do not work properly
with Python 3.X (I'm getting tracebackng about bytes vs str)



--
Rodrigo Siqueira
Graduate Student
Department of Computer Science
University of São Paulo



Bug#876274: wordpress: 9 security bugs in wordpress 4.8.1 and earlier

2017-09-22 Thread Rodrigo Campos
On Thu, Sep 21, 2017 at 04:26:53PM +0100, Rodrigo Campos wrote:
> On Thu, Sep 21, 2017 at 09:54:49AM +0200, Ángel wrote:
> > Salvatore wrote:
> > > have you identified already the issue -> fixing commit mappings?
> > 
> > For version 4.8.1 [buster, sid], upstream fixed them on 4.8.2
> > https://codex.wordpress.org/Version_4.8.2
> 
> And for jessie backports I'll update as soon as it is on sid :-)

It's already on sid and a backport is ready, will ask for BSA and craig will
upload when the BSA is assigned.



Thanks!
Rodrigo



Bug#876274: wordpress: 9 security bugs in wordpress 4.8.1 and earlier

2017-09-21 Thread Rodrigo Campos
On Thu, Sep 21, 2017 at 09:54:49AM +0200, Ángel wrote:
> Salvatore wrote:
> > have you identified already the issue -> fixing commit mappings?
> 
> For version 4.8.1 [buster, sid], upstream fixed them on 4.8.2
> https://codex.wordpress.org/Version_4.8.2

And for jessie backports I'll update as soon as it is on sid :-)



Bug#870909: RFS: cxlflash/4.3.2493-1 [ITP] -- IBM Data Engine for NoSQL Software Libraries

2017-09-21 Thread Rodrigo

Hi,

We've made a new upload. Please, consider this .dsc -> 
https://mentors.debian.net/debian/pool/main/c/cxlflash/cxlflash_4.3.2560-1.dsc



Thanks,
Rodrigo R. Galvao



Bug#870909: RFS: cxlflash/4.3.2493-1 [ITP] -- IBM Data Engine for NoSQL Software Libraries

2017-09-18 Thread Rodrigo

Hi,


The latest version of this package fix the issues pointed in the 
previous comment, as well as other points made in mentors.debian.


Here is the link to the .dsc -> 
https://mentors.debian.net/debian/pool/main/c/cxlflash/cxlflash_4.3.2554-1.dsc



Thanks,
Rodrigo R. Galvao



Bug#717736: liboggplay1: pkg-config aberrations: non-private Requires; -uninstalled.pc is installed

2017-09-13 Thread Rodrigo Siqueira Jordão


Hi Dafydd Harries,

I adopted this package as a way to learn more about packaging and  
Debian community. As result, I intend to keep this package in a good  
shape. I already updated the package and I am working to update it for  
debhelper 10.


I looked at the bug report and your patch. As far as I understood  
"Requires.private" and other stuff does not exist in the new package  
version. If you still interested in this problem, please let me know.  
Otherwise, I will close this bug soon.

--
Rodrigo Siqueira
Graduate Student
Department of Computer Science
University of São Paulo



Bug#738298: ITA

2017-08-29 Thread Rodrigo Siqueira Jordão

I am studying Debian package and I want to adopt pdfrw.

I am already working to update the package and I will be able to  
upload a new version soon.


--
Rodrigo Siqueira
Graduate Student
Department of Computer Science
University of São Paulo



Bug#870909: RFS: cxlflash/4.3.2493-1 [ITP] -- IBM Data Engine for NoSQL Software Libraries

2017-08-28 Thread Rodrigo

Hi,


This upload has the changes pointed by Michael in the previous message 
-> 
https://mentors.debian.net/debian/pool/non-free/c/cxlflash/cxlflash_4.3.2533-1.dsc



Thanks,
Rodrigo R. Galvao



Bug#870909: RFS: cxlflash/4.3.2493-1 [ITP] -- IBM Data Engine for NoSQL Software Libraries

2017-08-28 Thread Rodrigo

Hi Andrey,


> > There are a lot of errors in the install_root_man1 target.
> > There are warnings about unused ${perl:Depends}.
>
>
> We've made changes that should fix these errors. Could you check it,
> please? ->
> 
https://mentors.debian.net/debian/pool/non-free/c/cxlflash/cxlflash_4.3.2528-1.dsc



We uploaded the package to mentors.debian again. Please, consider this 
link now -> 
https://mentors.debian.net/debian/pool/non-free/c/cxlflash/cxlflash_4.3.2531-1.dsc



Thanks,
Rodrigo R. Galvao



Bug#870909: RFS: cxlflash/4.3.2493-1 [ITP] -- IBM Data Engine for NoSQL Software Libraries

2017-08-24 Thread Rodrigo

Hi Andrey,


> There are a lot of errors in the install_root_man1 target.
> There are warnings about unused ${perl:Depends}.


We've made changes that should fix these errors. Could you check it, 
please? -> 
https://mentors.debian.net/debian/pool/non-free/c/cxlflash/cxlflash_4.3.2528-1.dsc


Thanks,
Rodrigo R. Galvao



Bug#870909: RFS: cxlflash/4.3.2493-1 [ITP] -- IBM Data Engine for NoSQL Software Libraries

2017-08-24 Thread Rodrigo

Hi Andrey,

>> I was able to build from the link I sent to you using 'debuild -us -uc'.
>> Could you share with us what's the error, please?
> cflash_block_kern_mc.c:59:10: fatal error: scsi/cxlflash_ioctl.h: No 
such file or directory


We made some changes that fix this build problem. Here is the link to 
the .dsc -> 
https://mentors.debian.net/debian/pool/non-free/c/cxlflash/cxlflash_4.3.2524-1.dsc


Other doubt about the 'non-free' section: after read the link you shared 
with us, it says to send an email to <nonf...@release.debian.org> 
explaining why the package can be auto-built. So, should we send this 
email right now or wait for this process of sponsorship?



Thanks,
Rodrigo R. Galvao



Bug#870909: RFS: cxlflash/4.3.2493-1 [ITP] -- IBM Data Engine for NoSQL Software Libraries

2017-08-23 Thread Rodrigo

Hi,

> I don't really see any changes and also you haven't answered many of 
my questions.

> Also, the package doesn't build. Please don't upload packages you haven't
> tested.

I was able to build from the link I sent to you using 'debuild -us -uc'. 
Could you share with us what's the error, please?



Thanks,
Rodrigo R. Galvao



Bug#870909: RFS: cxlflash/4.3.2493-1 [ITP] -- IBM Data Engine for NoSQL Software Libraries

2017-08-23 Thread Rodrigo

Hi Andrey,

We've made some changes and uploaded it again, here is the link -> 
https://mentors.debian.net/debian/pool/main/c/cxlflash/cxlflash_4.3.2520-1.dsc


About the "non-free", how does it work? I mean, we have to change some 
file in specific? (i.e. debian/control)



Thanks,
Rodrigo R. Galvao



Bug#870909: RFS: cxlflash/4.3.2493-1 [ITP] -- IBM Data Engine for NoSQL Software Libraries

2017-08-22 Thread Rodrigo

Hi Andrey,

We've made new changes, here is the link to the .dsc file -> 
https://mentors.debian.net/debian/pool/main/c/cxlflash/cxlflash_4.3.2520-1.dsc



> > > Please switch to the debhelper compat level 10.
> Not fixed.
The debhelper version is set to (>= 10) on debian/control. Is that what 
you meant?



> > > Why do you explicitly B-D on GCC 5?
> Not answered.
>
> > > Why do you B-D on libudev1 and libcxl1?
> Not answered.

Those libs were removed from Build-Depends.


> > > Why Vcs-Git but no Vcs-Browser?
> Not answered.

The source code is only on GitHub, that's why we used only Vcs-Git. Is 
that correct?



> > > Please remove commented out sample lines from debian/rules.
> Not fixed.

Done.


> What is debian/cxlflash-test.control?

The file was removed.


> What are ibmcapikv and afuimage?

Those are the previous names for the cxlflash packages, which could 
exist on a machine.



> Why libcflsh_usfs-0.so exports symbols from libc?

The usfc software has been removed, so there are no symbols related with 
libcflsh_usfs-0.so anymore.



Thanks,
Rodrigo R. Galvao



Bug#870909: RFS: cxlflash/4.3.2493-1 [ITP] -- IBM Data Engine for NoSQL Software Libraries

2017-08-21 Thread Rodrigo

Hi Andrey,

We changed some things based on the points you made. I uploaded the 
package again to mentors.debian, here is the link to the .dsc file -> 
https://mentors.debian.net/debian/pool/main/c/cxlflash/cxlflash_4.3.2518-1.dsc


Regarding the shared libs, they are installed together in the cxlflash 
package, so they'll all be sync'd in the build process. Besides, we 
commit to never change a shared library published interface in a way it 
breaks the binary compatibility, so any binary can work with any shared 
lib version.


> Maintainer and Uploaders contain the same mpvag...@us.ibm.com email.
> Priority should be optional.
> Current Standards-Version is 4.0.1.
> Please switch to the debhelper compat level 10.
> Why do you explicitly B-D on GCC 5?
> Why do you B-D on libudev1 and libcxl1?
> Why Vcs-Git but no Vcs-Browser?
> Vcs-Git gives 404.
> Please don't set DH_VERBOSE=1 and DH_OPTIONS=-v.
> Please remove commented out sample lines from debian/rules.
> Why are you running dh_install in override_dh_auto_install?
> Why is override_dh_gencontrol needed?
> override_dh_installdeb looks ugly and problematic.
> Maintainer scripts don't have debhelper markers.
> Why are you skipping dh_testroot?
> debian/source/include-binaries lists files that don't exist, doesn't it?
> How are you going to handle soname changes if you ship shared libs in a
> non-lib package?



Thanks,
Rodrigo R. Galvao



Bug#791527: ITA

2017-08-18 Thread Rodrigo Siqueira Jordão

Hi,

I am studying Debian package and I want to adopt liboggplay. I am  
already working to update the package and I will be able to upload a  
new version soon.

--
Rodrigo Siqueira
Graduate Student
Department of Computer Science
University of São Paulo



Bug#870909: RFS: cxlflash/4.3.2493-1 [ITP] -- IBM Data Engine for NoSQL Software Libraries

2017-08-14 Thread Rodrigo

Hi,

Here is the link for the .dsc file in mentors.debian -> 
https://mentors.debian.net/debian/pool/main/c/cxlflash/cxlflash_4.3.2493-1.dsc


P.S. sorry for the previous html message, I sent it by mistake.


Thanks,
Rodrigo R. Galvao



Bug#870909: RFS: cxlflash/4.3.2493-1 [ITP] -- IBM Data Engine for NoSQL Software Libraries

2017-08-09 Thread Rodrigo Rosatti Galvao
Hi Fred,> I didn't check deep but I can see that the packaging is not following> the latest policy manual (newer-standards-version) : have a look to this> document (> https://www.debian.org/doc/packaging-manuals/upgrading-checklist.txt )> to fix this ; https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Standards-Version
I've checked and the current Standards-Version is the latest: 4.0.0
 > Also, could you make the debian/watch file work please ?
The watch file is working now. I uploaded the package to debian/mentors again after these changes.  
Thanks,Rodrigo R. Galvão
 
 
 
- Original message -From: Frédéric Bonnard <fre...@linux.vnet.ibm.com>To: 870...@bugs.debian.org, Rodrigo Rosatti Galvao/Brazil/IBM@IBMBRCc:Subject: Bug#870909: RFS: cxlflash/4.3.2493-1 [ITP] -- IBM Data Engine for NoSQL Software LibrariesDate: Mon, Aug 7, 2017 8:36 AM 
Hi Rodrigo,I do not intend to sponsor this package but I'm just willing to help.Be careful to target "Package: sponsorship-request*s*" : the bug as beenproperly re-assigned to "sponsorship-requests", but it didn't reach thementors audience as I can tell.I didn't check deep but I can see that the packaging is not followingthe latest policy manual (newer-standards-version) : have a look to thisdocument (https://www.debian.org/doc/packaging-manuals/upgrading-checklist.txt )to fix this ; https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Standards-VersionAlso, could you make the debian/watch file work please ?Thanks,F.> Package: sponsorship-request> Severity: normal>> Dear mentors,>>  I am looking for a sponsor for my package "cxlflash">> * Package name    : cxlflash>   Version         : 4.3.2493-1>   Upstream Author : Mike Vageline <mpvag...@us.ibm.com>> * URL             : https://github.com/open-power/capiflash> * License         : GPL-2+, Apache-2.0>   Section         : utils>>  It builds those binary packages:>>     cxlflash   - IBM Data Engine for NoSQL Software>     Libraries : cxlflash>     cxlflashimage - IBM Data Engine for NoSQL Software>     Libraries : cxlflash afu libra>>  To access further information about this package, please visit the following URL:>  https://mentors.debian.net/package/cxlflash>>>  Alternatively, one can download the package with dget using this command:>>    dget -x>    https://mentors.debian.net/debian/pool/main/c/cxlflash/cxlflash_4.3.2493-1.dsc>>  More information about hello can be obtained from>  https://github.com/open-power/capiflash.>>>  Regards,>    Rodrigo R. Galvao
 
attak89f.datType: application/pgp-signatureName: attak89f.dat
 



attfp5dt.dat
Description: Binary data


Bug#870909: RFS: cxlflash/4.3.2493-1 [ITP] -- IBM Data Engine for NoSQL Software Libraries

2017-08-09 Thread Rodrigo

Hi Fred,

> I didn't check deep but I can see that the packaging is not following
> the latest policy manual (newer-standards-version) : have a look to this
> document (
> https://www.debian.org/doc/packaging-manuals/upgrading-checklist.txt )
> to fix this ; 
https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Standards-Version


I've checked and the current Standards-Version is the latest: 4.0.0

> Also, could you make the debian/watch file work please ?
The watch file is working now. I uploaded the package to debian/mentors 
again after these changes.


Thanks,

Rodrigo R. Galvão



Bug#870909: RFS: cxlflash/4.3.2493-1 [ITP] -- IBM Data Engine for NoSQL Software Libraries

2017-08-06 Thread Rodrigo R. Galvao
Package: sponsorship-request
Severity: normal

Dear mentors,

 I am looking for a sponsor for my package "cxlflash"

* Package name: cxlflash
  Version : 4.3.2493-1
  Upstream Author : Mike Vageline <mpvag...@us.ibm.com>
* URL : https://github.com/open-power/capiflash
* License : GPL-2+, Apache-2.0
  Section : utils

 It builds those binary packages:

cxlflash   - IBM Data Engine for NoSQL Software 
Libraries : cxlflash
cxlflashimage - IBM Data Engine for NoSQL Software 
Libraries : cxlflash afu libra

 To access further information about this package, please visit the following 
URL:
 https://mentors.debian.net/package/cxlflash


 Alternatively, one can download the package with dget using this command:

   dget -x 
   
https://mentors.debian.net/debian/pool/main/c/cxlflash/cxlflash_4.3.2493-1.dsc

 More information about hello can be obtained from
 https://github.com/open-power/capiflash.


 Regards,
   Rodrigo R. Galvao



Bug#870487: ITP: cxlflash -- Provides configuration and device management services for CAPI flash accelerators.

2017-08-02 Thread Rodrigo R. Galvao
Package: wnpp
Severity: wishlist
Owner: "Rodrigo R. Galvao" <rosat...@br.ibm.com>

* Package name: cxlflash
  Version : 4.3.2488
  Upstream Author : Mike Vageline <mpvag...@us.ibm.com>
* URL : https://github.com/open-power/capiflash
* License : GPL-2+, Apache-2.0
  Programming Lang: C
  Description : Provides configuration and device management
  services for CAPI flash accelerators.

CAPI can be thought of as a special tunneling protocol through PCIe that
allow PCIe adapters to look like special purpose co-processors which can
read or write an application's memory and generate page faults. 
The cxlflash driver is responsible for the initialization of the Coherent
Accelerator (CXL) Flash Adapter, setting up the special path for user
space access, and performing error recovery.



Bug#701599: lightdm 1.18.3-1 breaks multiseat support

2017-07-28 Thread Rodrigo Fresneda
Package: lightdm
Followup-For: Bug #701599

Dear Maintainer,

after upgrade to version 1.18.3-1 my xorg multiseat configuration stopped
working
(the second monitor did not receive any input).
Rolling back to version 1.10.3-3 solves the problem.



-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages lightdm depends on:
ii  adduser3.115
ii  dbus   1.10.18-1
ii  debconf [debconf-2.0]  1.5.61
ii  libc6  2.24-11+deb9u1
ii  libgcrypt201.7.6-2+deb9u1
ii  libglib2.0-0   2.50.3-2
ii  libpam-systemd 232-25+deb9u1
ii  libpam0g   1.1.8-3.6
ii  libxcb11.12-1
ii  libxdmcp6  1:1.1.2-3
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.2-1

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+19
Versions of packages lightdm suggests:
ii  accountsservice  0.6.43-1
ii  upower   0.99.4-4+b1

-- Configuration Files:
/etc/lightdm/lightdm.conf changed:
[LightDM]
greeter-user=lightdm
minimum-display-number=0
minimum-vt=1
log-directory=/var/log/lightdm
run-directory=/run/lightdm
xserver-command = /usr/bin/X
 greeter-session = lightdm-gtk-greeter
 greeter-show-manual-login = true
 user-session = mate
exit-on-failure = true
[SeatDefaults]
xserver-config= xorg.conf
exit-on-failure=true
[Seat:0]
xserver-command=/usr/bin/X :0 -sharevts  -isolateDevice PCI:2:0:0
xserver-layout=Layout0
[Seat:1]
xserver-command=/usr/bin/X :1 -sharevts -isolateDevice PCI:3:0:0
xserver-layout=Layout1
[XDMCPServer]
[VNCServer]


-- debconf information:
* shared/default-x-display-manager: lightdm
  lightdm/daemon_name: /usr/sbin/lightdm


Bug#827414:

2017-07-28 Thread Rodrigo Aguilera
I think rygel is not a desktop application so that is not the appropriate way.
Does rygel comes with some kind of file that alllows you to manage it as a 
service with systemd?


Bug#851066: More security bugs in debian version

2017-05-20 Thread Rodrigo Campos
Hi,

Just in case you weren't aware, several security issues has been fixed in flash.
Here is the last batch of fixes that I know of:
https://blog.qualys.com/laws-of-vulnerabilities/2017/05/09/adobe-fixes-half-dozen-flash-vulnerabilities-and-more

These is, of course, not fixed in debian because of this bug.


If I can help with testing or something, please let me know.



Thanks,
Rodrigo



Bug#862816: wordpress: Six security bugs in wordpress 4.7.4 and earlier

2017-05-17 Thread Rodrigo Campos
On Wed, May 17, 2017 at 09:54:55PM +1000, Craig Small wrote:
> Source: wordpress
> Version: 4.7.4+dfsg-1
> Severity: grave
> Tags: upstream security
> Justification: user security hole
> 
> Wordpress 4.7.4 and earlier has 6 security holes that are fixed in
> 4.7.5[1]
> 
>  * 2.7.0 - 4.7.4
>Insufficient redirect validation in the HTTP class.
>  * 2.5.0 - 4.7.4
>Improper handling of post meta data values in the XML-RPC API.
>  * 3.4.0 - 4.7.4
>Lack of capability checks for post meta data in the XML-RPC API.
>  * 2.5.0 - 4.7.4
>A Cross Site Request Forgery (CRSF) vulnerability was discovered in the
>filesystem credentials dialog.
>  * 3.3 - 4.7.4
>A cross-site scripting (XSS) vulnerability was discovered when
>attempting to upload very large files.
>  * 3.4.0 - 4.6.4
>A cross-site scripting (XSS) vulnerability was discovered related to the
>Customizer.
> 
> Looking at the versions, all distributions are vulnerable to all bugs,
> yay me!

Craig, will this version make it to testing? If that is the case, I'll prepare
the jessie backport today.



Thanks a lot,
Rodrigo



Bug#860059: gdm3: Window lag

2017-04-10 Thread Rodrigo
Package: gdm3
Version: 3.14.1-7
Severity: important

Description:

Most of the time, all windows behave strangely. It's like they don't update
what they should show until you force change what they should display. For 
example: if I'm on rhytmbox acrolling some list with up and down arrows,
sometimes the screen does not show my latest button press. If I press it
again, it is noticeable that the key was pressed twice, even though it only
shows that at the second key press.



-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages gdm3 depends on:
ii  accountsservice   0.6.37-3+b1
ii  adduser   3.113+nmu3
ii  dconf-cli 0.22.0-1
ii  dconf-gsettings-backend   0.22.0-1
ii  debconf [debconf-2.0] 1.5.56
ii  gir1.2-gdm3   3.14.1-7
ii  gnome-session [x-session-manager] 3.14.0-2
ii  gnome-session-bin 3.14.0-2
ii  gnome-settings-daemon 3.14.2-3
ii  gnome-shell   3.14.4-1~deb8u1
ii  gnome-terminal [x-terminal-emulator]  3.14.1-1+deb8u1
ii  gsettings-desktop-schemas 3.14.1-1
ii  libaccountsservice0   0.6.37-3+b1
ii  libaudit1 1:2.4-1+b1
ii  libc6 2.19-18+deb8u7
ii  libcanberra-gtk3-00.30-2.1
ii  libcanberra0  0.30-2.1
ii  libgdk-pixbuf2.0-02.31.1-2+deb8u5
ii  libgdm1   3.14.1-7
ii  libglib2.0-0  2.42.1-1+b1
ii  libglib2.0-bin2.42.1-1+b1
ii  libgtk-3-03.14.5-1+deb8u1
ii  libpam-modules1.1.8-3.1+deb8u2
ii  libpam-runtime1.1.8-3.1+deb8u2
ii  libpam-systemd215-17+deb8u6
ii  libpam0g  1.1.8-3.1+deb8u2
ii  librsvg2-common   2.40.5-1+deb8u2
ii  libselinux1   2.3-2
ii  libsystemd0   215-17+deb8u6
ii  libwrap0  7.6.q-25
ii  libx11-6  2:1.6.2-3
ii  libxau6   1:1.0.8-1
ii  libxdmcp6 1:1.1.1-1+b1
ii  libxrandr22:1.4.2-1+b1
ii  lsb-base  4.1+Debian13+nmu1
ii  metacity [x-window-manager]   1:3.14.3-1
ii  mutter [x-window-manager] 3.14.4-1~deb8u1
ii  policykit-1   0.105-15~deb8u2
ii  ucf   3.0030
ii  x11-common1:7.7+7
ii  x11-xserver-utils 7.7+3+b1
ii  xterm [x-terminal-emulator]   312-2

Versions of packages gdm3 recommends:
ii  at-spi2-core   2.14.0-1
ii  desktop-base   8.0.2
ii  gnome-icon-theme   3.12.0-1
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  x11-xkb-utils  7.7+1
ii  xserver-xephyr 2:1.16.4-1
ii  xserver-xorg   1:7.7+7
ii  zenity 3.14.0-1

Versions of packages gdm3 suggests:
ii  gnome-orca3.14.0-4+deb8u1
ii  libpam-gnome-keyring  3.14.0-1+b1

-- debconf information:
  gdm3/daemon_name: /usr/sbin/gdm3
* shared/default-x-display-manager: gdm3



Bug#854869: wordpress: please consider to package and enable by default disable REST API plugin

2017-02-16 Thread Rodrigo Campos
On Sat, Feb 11, 2017 at 12:18:06PM +0100, Martin Steigerwald wrote:
> Package: wordpress
> Version: 4.7.2+dfsg-1~bpo8+1
> Severity: normal
> 
> Dear Craig,
> 
> thanks for your notice on your blog. Fortunately Rodrigo was fast with
> the backport. And I think I installed the update before disclosure.

Glad it was on time :)

> 
> According to
> 
> https://make.wordpress.org/core/2017/02/01/disclosure-of-additional-security-fix-in-wordpress-4-7-2/
> 
> the security issue was in a feature I do not use on any of my sites.
> 
> Additionally since Wordpress 4.7.2 it is not possible to disable that
> feature without installing a plugin like
> 
> https://de.wordpress.org/plugins/disable-json-api/
> 
> I do think this is a highly questionable approach to security that upstream
> goes there, and if upstream insists on continuing this despite all the 
> comments
> and requests to disable that feature by default, I ask you to take such
> measures in downstream package.

Do you have links for upstream statements about not reconsidering making it an
option?

Not that I doubt about it, don't get me wrong, but just want to see how they
communicated it, because it seems something difficult to tell it is not an
*option* anymore :)

> So please consider packaging and enabling by default the above plugin in
> case upstream developers do not change their approach to prioritize security
> over enabling features by default that not everyone need.o

Just curious (sorry, I am no longer using wordpress at $DAYJOB and I'm not
really up to date), but can't you just block requests to:

/wp-json/

on your webserver? That isn't enough or will it cause some other problems
because plugins use that? In that case, maybe you can block it at the web server
layer allowing only certain IPs?




Thanks a lot,
Rodrigo



Bug#845996: needrestart: Restarts lxdm by default

2016-11-28 Thread Rodrigo Campos
On Sun, Nov 27, 2016 at 05:45:24PM +0100, Thomas Liske wrote:
> 
> Hi Rodrigo,
> 
> Rodrigo Campos <rodr...@sdfg.com.ar> writes:
> > I'm using lxdm display manager and needrestart tries to restart it by 
> > default,
> > instead of being disabled by default as it is with others DM.
> 
> I've added an override to the default configuration at upstream[1]. Thanks
> for reporting.
> 
> [1] 
> https://github.com/liske/needrestart/commit/2bf61d8f65a03fb6ecec2ddbb16e27100ba04c40

Thank you! :)



Bug#845996: needrestart: Restarts lxdm by default

2016-11-27 Thread Rodrigo Campos
Package: needrestart
Version: 2.10-1
Severity: normal

Dear Maintainer,

I'm using lxdm display manager and needrestart tries to restart it by default,
instead of being disabled by default as it is with others DM.

The attached patch adds this behaviour for LXDM too. Please consider merging
this or fixing it some other way.




Thanks,
Rodrigo


ackage-specific info:
needrestart output:
Your outdated processes:
alsamixer[4907], at-spi-bus-laun[2822], at-spi2-registr[2850], bash[3098, 5690, 
8655, 2836], dbus-daemon[2832, 2740], gconfd-2[2981], goa-daemon[12274],
 goa-identity-se[12282], gvfs-afc-volume[12265], gvfsd[2862], 
gvfsd-http[32454], gvfsd-metadata[12461], gvfsd-trash[12319], 
gvfs-gphoto2-vo[12311],
 gvfs-mtp-volume[12261], gvfs-udisks2-vo[12251], hexchat[22160], 
mission-control[12288], mosh-client[5708], pidgin[22173], pulseaudio[2841], 
systemd[2718],
 transmission-re[23254], wicd-client[2824], xbrlapi[2759], xfce4-clipman[2826], 
xfce4-terminal[3090], xfconfd[2859], xterm[2801], zeitgeist-daemo[2876],
 zeitgeist-datah[2825], zeitgeist-fts[2906]

checkrestart output:


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'proposed-updates'), (500, 'stable'), 
(400, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages needrestart depends on:
ii  dpkg   1.18.15
ii  gettext-base   0.19.8.1-1
ii  libintl-perl   1.26-2
ii  libmodule-find-perl0.13-1
ii  libmodule-scandeps-perl1.22-1
ii  libproc-processtable-perl  0.53-2
ii  libsort-naturally-perl 1.03-1
ii  libterm-readkey-perl   2.37-1
ii  perl   5.24.1~rc3-3
ii  xz-utils   5.2.2-1.2

needrestart recommends no packages.

Versions of packages needrestart suggests:
ii  libnotify-bin  0.7.7-1

-- Configuration Files:
/etc/needrestart/needrestart.conf changed [not included]

-- no debconf information

--- ./ex/needrestart.conf	2016-11-27 12:34:55.624082819 -0300
+++ ./ex/needrestart.conf.path	2016-11-27 12:34:49.271959331 -0300
@@ -81,6 +81,7 @@
 q(^xdm) => 0,
 q(^lightdm) => 0,
 q(^slim) => 0,
+q(^lxdm) => 0,
 
 # networking stuff
 q(^network-manager) => 0,


Bug#837364: virtualbox: After update VMs still in "starting virtual machine ..."

2016-09-10 Thread Rodrigo Ramírez Norambuena
Package: virtualbox
Version: 5.1.4-dfsg-1+b1
Severity: normal
Tags: upstream

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

After an upgrade into branch stretch/sid to 5.1.4-dfsg-1+b1 when I try
run a VirtualMachine the window still with message "Starting virtual machine
..."


   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I some search, the file ~/.VirtualBox/VBoxSVC.log output

"
 00:08:32.932717 nspr-7 Failed to open "/dev/vboxdrvu", errno=13,
rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
 00:08:33.555836 nspr-6 Failed to open "/dev/vboxdrvu", errno=13,
rc=VERR_VM_DRIVER_NOT_ACCESSIBLE
"


The permision of file driver has 0600
 $ ls -lh /dev/vboxdrvu
 crw--- 1 root root 10, 56 Sep 10 12:47 /dev/vboxdrvu


If is changed the permission to 0666 is possible run a VMs normally



*** End of the template - remove these template lines ***



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

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

Versions of packages virtualbox depends on:
ii  adduser   3.115
ii  init-system-helpers   1.42
ii  libc6 2.23-5
ii  libcurl3-gnutls   7.50.1-1
ii  libgcc1   1:6.1.1-11
ii  libgsoap9 2.8.30-1
ii  libpng16-16   1.6.24-2
ii  libpython2.7  2.7.12-3
ii  libsdl1.2debian   1.2.15+dfsg1-4
ii  libssl1.0.2   1.0.2h-1
ii  libstdc++66.1.1-11
ii  libvncserver1 0.9.10+dfsg-3+b1
ii  libvpx4   1.6.0-2
ii  libx11-6  2:1.6.3-1
ii  libxcursor1   1:1.1.14-1+b1
ii  libxext6  2:1.3.3-1
ii  libxml2   2.9.4+dfsg1-1+b1
ii  libxmu6   2:1.1.2-2
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-2
ii  python2.7 2.7.12-3
pn  python:any
ii  virtualbox-dkms [virtualbox-modules]  5.1.4-dfsg-1
ii  virtualbox-source 5.1.4-dfsg-1
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages virtualbox recommends:
ii  libgl1-mesa-glx [libgl1]  11.2.2-1
ii  libqt5core5a  5.6.1+dfsg-3+b1
ii  libqt5opengl5 5.6.1+dfsg-3+b1
ii  libqt5widgets55.6.1+dfsg-3+b1
ii  virtualbox-qt 5.1.4-dfsg-1+b1

Versions of packages virtualbox suggests:
pn  vde2
pn  virtualbox-guest-additions-iso  

-- no debconf information



Bug#825292: grub-common: does not provide the correct device name for booting the Hurd.

2016-06-01 Thread Rodrigo Valiña Gutiérrez
El 30/5/2016 21:07, "Samuel Thibault"  escribió:
>
> Yes, that should be correct. Note that it's the 30_os-prober.in file
> which needs to be modified. Also, since this is an upstream file, you
> should probably contact upstream to get it integrated there, so Debian
> doesn't maintain the change ad æternam.
>

Ok. Reported upstream at:

http://savannah.gnu.org/bugs/?48068


Bug#825696: golang: new upstream release (1.6.2)

2016-05-28 Thread Rodrigo Campos
Package: golang
Version: 2:1.6.1-2
Severity: normal

Hi,

There is a new version, 1.6.2, available. I'm particularly interested because
I'm hitting a bug in the net/http package that is fixed 1.6.2.

Can you please upgrade?



Thanks a lot,
Rodrigo



Bug#825292: grub-common: does not provide the correct device name for booting the Hurd.

2016-05-26 Thread Rodrigo Valiña Gutiérrez
On Wed, May 25, 2016 at 11:20 PM, Samuel Thibault <sthiba...@debian.org>
wrote:

>
> Why adding another variable, instead of just fixing mach_device?  I
> guess grub-probe simply changed something and the mach_device definition
> needs to be updated.
>
> This is really meant to be a mach device name, not a "hurd device name".
>
> Samuel
>

I understand. I did not know the exact terminology. So the patch might boil
down to:

-
--- 30_os-prober2016-02-05 18:30:35.0 +0100
+++ 30_os-prober-32016-05-26 11:54:35.819822599 +0200
@@ -331,7 +331,7 @@
   save_default_entry | grub_add_tab
   prepare_grub_to_access_device ${DEVICE} | grub_add_tab
   grub_device="`${grub_probe} --device ${DEVICE} --target=drive`"
-  mach_device="`echo "${grub_device}" | sed -e
's/(\(hd.*\),msdos\(.*\))/\1s\2/'`"
+  mach_device=`${grub_probe} --device ${DEVICE}
--target=compatibility_hint | sed 's/,msdos/s/'`
   grub_fs="`${grub_probe} --device ${DEVICE} --target=fs`"
   case "${grub_fs}" in
 *fs)hurd_fs="${grub_fs}" ;;
-

So this is one more step to get working flawlessly and out of the box the
procedure at:
https://www.gnu.org/software/hurd/hurd/running/debian/CrossInstall.html
It remains at least to determine whether --readonly is needed, and maybe to
provide a way to boot in single user mode (-s) (needed for the first two
reboots).
By the moment it does not work out of the box yet because of these and
maybe other issues.
Rodrigo.


Bug#825292: grub-common: does not provide the correct device name for booting the Hurd.

2016-05-25 Thread Rodrigo Valiña Gutiérrez
Package: grub-common
Version: 2.02~beta2-22+deb8u1
Severity: normal
Tags: patch

The script /etc/grub.d/30_os-prober does not provide the correct device name
for booting the Hurd, e.g. when installed with crosshurd.
The bug also applies to the grub version currently in sid.

The patch changes provided device names from, e.g.:
  (hostdisk//dev/sda,msdos2)
to:
  hd0s2

This is the patch that solved the problem in my case, and may be correct:

-
--- 30_os-prober2016-02-05 18:30:35.0 +0100
+++ 30_os-prober-2  2016-05-25 17:13:17.518318125 +0200
@@ -332,13 +332,14 @@
   prepare_grub_to_access_device ${DEVICE} | grub_add_tab
   grub_device="`${grub_probe} --device ${DEVICE} --target=drive`"
   mach_device="`echo "${grub_device}" | sed -e 
's/(\(hd.*\),msdos\(.*\))/\1s\2/'`"
+  hurd_device=`${grub_probe} --device ${DEVICE} 
--target=compatibility_hint | sed 's/,msdos/s/'`
   grub_fs="`${grub_probe} --device ${DEVICE} --target=fs`"
   case "${grub_fs}" in
*fs)hurd_fs="${grub_fs}" ;;
*)  hurd_fs="${grub_fs}fs" ;;
   esac
   cat << EOF
-   multiboot /boot/gnumach.gz root=device:${mach_device}
+   multiboot /boot/gnumach.gz root=device:${hurd_device}
module /hurd/${hurd_fs}.static ${hurd_fs} --readonly \\
--multiboot-command-line='\${kernel-command-line}' \\
--host-priv-port='\${host-port}' \\
-



Bug#825229: crosshurd: Incompatibility with update-grub. Fails to boot.

2016-05-24 Thread Rodrigo Valiña Gutiérrez
Package: crosshurd
Version: 1.7.50
Severity: normal
Tags: patch

Running crosshurd to install in a disk partition and then running update-grub,
rebooting and selecting the Hurd entry, fails to boot because the Grub
does not find /boot/gnumach.gz (there is /boot/gnumach-1.6-486.gz).

The following patch solves the problem in my case:

-
--- makehurddir.sh  2016-05-22 16:28:32.0 +0200
+++ makehurddir2.sh 2016-05-24 21:25:48.678706572 +0200
@@ -43,6 +43,8 @@
 
 if [ -e $TARGET/var/cache/apt/archives/gnumach-image-1.6-486_* ] ; then
 extract gnumach-image-1.6-486
+# place symlink for compatibility with update-grub 
(/etc/grub.d/30_os-prober)
+ln -s gnumach-1.6-486.gz "$TARGET/boot/gnumach.gz"
 fi
 
 if [ -e $TARGET/var/cache/apt/archives/libbz2-1.0_* ] ; then
-

Afterwards, the Hurd starts to boot but fails (hangs) with the following error
(maybe an issue with partition names):

start ext2fs: ext2fs: device:(hostdisk//dev/sda,msdos2): No such device or 
address

Also I have observed that, running "grep TARGET /usr/share/crosshurd/*"
yields some results with "$TARGET/..." quoted and some others not,
so if we run crosshurd with a path with spaces, it may fail.



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

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

Versions of packages crosshurd depends on:
ii  dialog1.2-20140911-1
ii  dpkg-dev  1.17.26

Versions of packages crosshurd recommends:
pn  attr  

crosshurd suggests no packages.

-- no debconf information



Bug#598427:

2016-05-18 Thread Rodrigo Valiña Gutiérrez
This bug also affects current version in unstable.
If you choose a base-unexistent path in crosshurd,
which subsequently will be passed to makehurddir.sh,
makehurddir.sh will call readlink -f,
which may return an empty string in some cases,
thus $TARGET will be "", so commands like:

 cp /etc/resolv.conf "$TARGET/etc/resolv.conf"

will end up overwriting some of root filesystem's files.

Do not try this as root !!!

Here is a possible patch for makehurddir.sh:


--- a/makehurddir.sh2016-02-21 23:28:54.0 +0100
+++ b/makehurddir.sh2016-05-18 17:07:46.578718033 +0200
@@ -10,6 +10,11 @@
 DEB_TARGET_GNU_CPU=$2
 DEB_TARGET_GNU_SYSTEM=$3

+if [ x"$TARGET" = x ]; then
+  echo "Refused to overwrite inexistent/empty TARGET."
+  exit 1
+fi
+
 . /usr/share/crosshurd/functions

 debs=`cat /etc/crosshurd/packages/{common,$DEB_TARGET_GNU_SYSTEM} |
grep -v '^#'`




Bug#818758: WordPress plugins depending on libphp-phpmailer > 5.2.10

2016-03-20 Thread Rodrigo Campos
On Sun, Mar 20, 2016 at 02:20:31PM +0100, David Raison wrote:
> Package: wordpress
> Version: 4.4.2+dfsg-1~bpo8+1

Please report bugs that you found in the packages to the backports mailing list
and NOT to the Debian BTS, it says here:

http://backports.debian.org/Instructions/#index6h2




Thanks!
Rodrigo



Bug#812557: pulseaudio: "refusing to start/autospawn" with multi-user setup

2016-02-16 Thread Rodrigo Campos
On Mon, Feb 15, 2016 at 07:54:17PM -0300, Felipe Sateler wrote:
> Control: tags -1 - moreinfo
> Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=94167
> 
> Thanks. Marking as forwarded accordingly.

Closed upstream, not sure if you want to close it here too :)



Bug#812557: pulseaudio: "refusing to start/autospawn" with multi-user setup

2016-02-15 Thread Rodrigo Campos
On Mon, Feb 15, 2016 at 07:46:22PM -0300, Felipe Sateler wrote:
> On 15 February 2016 at 19:41, Rodrigo Campos <rodr...@sdfg.com.ar> wrote:
> > On Mon, Feb 15, 2016 at 07:09:11PM -0300, Felipe Sateler wrote:
> >> On 15 February 2016 at 16:11, Rodrigo Campos <rodr...@sdfg.com.ar> wrote:
> >>
> >> >> Would you forward
> >> >> it upstream, then?
> >>
> >> No, sorry. When feedback will be requested by upstream then I won't be
> >> able to provide it. The only way, then, is for you to file the bug to
> >> the upstream bugzilla:
> >>
> >> http://bugs.freedesktop.org
> >
> > It seems sysmted uses github for issues, at least the link is to github 
> > here:
> > https://www.freedesktop.org/wiki/Software/systemd/. Am I missing something? 
> > I
> > didn't find it in http://bugs.freedesktop.org
> 
> Right, but this bug is against pulseaudio, not systemd ;)

Oh, fuck! I should take a rest. Thanks for pointing it out.

So, here is the bug for pulseaudio:
https://bugs.freedesktop.org/show_bug.cgi?id=94167 =)





Thanks,
Rodrigo



Bug#812557: pulseaudio: "refusing to start/autospawn" with multi-user setup

2016-02-15 Thread Rodrigo Campos
On Mon, Feb 15, 2016 at 07:09:11PM -0300, Felipe Sateler wrote:
> On 15 February 2016 at 16:11, Rodrigo Campos <rodr...@sdfg.com.ar> wrote:
> 
> >> Would you forward
> >> it upstream, then?
> 
> No, sorry. When feedback will be requested by upstream then I won't be
> able to provide it. The only way, then, is for you to file the bug to
> the upstream bugzilla:
> 
> http://bugs.freedesktop.org

It seems sysmted uses github for issues, at least the link is to github here:
https://www.freedesktop.org/wiki/Software/systemd/. Am I missing something? I
didn't find it in http://bugs.freedesktop.org

So, if it is relevant for someone else, here is the issue I created upstream:
https://github.com/systemd/systemd/issues/2629




Thanks a lot,
Rodrigo



Bug#812557: pulseaudio: "refusing to start/autospawn" with multi-user setup

2016-02-15 Thread Rodrigo Campos
Now with 812...@bugs.debian.org on "Cc:"

On Mon, Feb 15, 2016 at 07:11:04PM +0000, Rodrigo Campos wrote:
> On Mon, Feb 15, 2016 at 03:53:07PM -0300, Felipe Sateler wrote:
> > On 15 February 2016 at 13:23, Rodrigo Campos <rodr...@sdfg.com.ar> wrote:
> > > On Mon, Feb 15, 2016 at 12:58:58PM -0300, Felipe Sateler wrote:
> > >>
> > >> You can work around this by disabling the x11 publish module, via
> > >> disabling the autostart of start-pulseaudio-x11 (by removing/moving
> > >> away the /etc/xdg/autostart/pulseaudio.desktop file).
> > >
> > > Ohh, I can confirm that this workaround works.
> > >
> > >
> > > Let me know if you need more info or I can help you with testing the fix
> > 
> > I don't think there is anything we can do on the debian side. Maybe
> > you can raise the issue upstream and see whether they come up with a
> > way to support your use case? I don't think I want to deviate from
> > upstream in this respect.
> 
> I was not asking to deviate from upstream, just fix the bug. Would you forward
> it upstream, then?
> 
> 
> 
> 
> 
> Thanks a lot,
> Rodrigo



Bug#812557: pulseaudio: "refusing to start/autospawn" with multi-user setup

2016-02-15 Thread Rodrigo Campos
On Mon, Feb 15, 2016 at 12:58:58PM -0300, Felipe Sateler wrote:
> Control: tags -1 moreinfo
> 
> On 24 January 2016 at 22:42, Rodrigo Campos <rodr...@sdfg.com.ar> wrote:
> >
> > Package: pulseaudio
> > Version: 7.1-2
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > I'be updated debian testing (didn't update in a while) and after I upgraded,
> > sound from programs that run as a different user stopped working.
> >
> > When some other user tries to run: "/usr/bin/pulseaudio --start
> > --log-target=syslog" it fails with errors like:
> >
> > Jan 24 22:01:58 lindsay pulseaudio[10238]: [pulseaudio] main.c: 
> > User-configured
> > server at 
> > {d07a5e247c911a2ac8ca6d8652d822c1}unix:/run/user/1000/pulse/native,
> > refusing to start/autospawn.
> > Jan 24 22:08:13 lindsay pulseaudio[11867]: [pulseaudio] main.c: 
> > User-configured
> > server at lindsay, refusing to start/autospawn.
> >
> > Both users, the user that opened the desktop environment (let's call him 
> > userA)
> > and the other user trying to run pulseaudio/firefox (let's call him userB) 
> > are
> > member of group audio. Also, userA uid is 1000 and userB uid is 1001.
> 
> How are you running firefox/pulseaudio as different users? Just sudo
> -u userB firefox or some other way?

Yes, just that. And also run: "xhost +SI:localuser:userB" before.

> > Usually, as autospawn is enabled, when running firefox as userB and sound
> > was needed, pulseaudio was started and audio just worked. Now everything 
> > works
> > fine, except audio doesn't play. Probably because it fails as above when 
> > trying
> > to start pulseaudio.
> >
> > I've found the following work-around, though, to make this work again and 
> > this
> > is why I'm reporting it to pulseaudio.
> >
> > If userA logins to the desktop env and opens a console and as userB (I'm 
> > doing
> > "su - userB") runs:
> >
> > pax11publish -r; /usr/bin/pulseaudio --start --log-target=syslog
> >
> > then audio works again.
> 
> OK, this is the x11 publish module.
> 
> >
> > To check if audio works, and to be sure is nothing related to firefox, I 
> > run as
> > userA in the desktop env:
> >
> > sudo -u userB -- aplay /usr/share/sounds/alsa/Front_Center.wav
> >
> > iAfter doing the "pax11publish ..." command above, this command works. 
> > Before it
> > does not. And, of course, this also fixes the audio in firefox.
> 
> You can work around this by disabling the x11 publish module, via
> disabling the autostart of start-pulseaudio-x11 (by removing/moving
> away the /etc/xdg/autostart/pulseaudio.desktop file).

Ohh, I can confirm that this workaround works.


Let me know if you need more info or I can help you with testing the fix





Thanks a lot,
Rodrigo



Bug#812557: Acknowledgement (pulseaudio: "refusing to start/autospawn" with multi-user setup)

2016-02-01 Thread Rodrigo Campos
ping? :)



Bug#812557: Acknowledgement (pulseaudio: "refusing to start/autospawn" with multi-user setup)

2016-02-01 Thread Rodrigo Campos
On Mon, Feb 01, 2016 at 03:18:14PM -0300, Felipe Sateler wrote:
> On 1 Feb 2016 09:42, "Rodrigo Campos" <rodr...@sdfg.com.ar> wrote:
> >
> > ping? :)
> 
> Hi, sorry I am out of town so I have not taken a look. But using the same

Oh, no problem. Let me know when you are back :-)

> server for multiple users requires a small amount of setup. Please look up
> how to setup the pulseaudio cookie for the second user (on my phone now, so
> its difficult to look up).

It have always worked in the past, and I found a workaround that it's in the
original report. The issue doesn't seem to be sharing the cookie, but using 2
pulse audio servers (one run by each user).

> 
> Saludos

Saludos! :-)



Bug#813228: Thanks

2016-01-30 Thread Rodrigo Campos
Yes, I know it's present in newer versions. Didn't know this is whishlist,
sorry. I tought it was normal as MITM attacks are easier when no cert validation
is done at all.

I asked because the SSLCiphers were backported (although that probably is an
even simpler patch) to 1.4 and thought this is an important feature too, and
hopefully not too invasive (the patch I linked is not a one line patch, but it
doesn't change A LOT. Although I don't know if it applies fine).

But if it won't be backported (whatever reason), I will probably not use the
jessie znc package.




Thanks a lot,
Rodrigo



Bug#813228: znc: doesn't validate TLS certificate of IRC server

2016-01-30 Thread Rodrigo Campos
Source: znc
Version: 1.4-2
Severity: normal

Dear Maintainer,

The version in jessie does not validates the certificate of the IRC server. Here
is the patch doing it that is merged upstream:

https://github.com/znc/znc/pull/761

I didn't try if it applies cleany to jessie, but I think it might.


Please let me know if I can help you with tests or something.




Thanks a lot,
Rodrigo



Bug#812557: pulseaudio: "refusing to start/autospawn" with multi-user setup

2016-01-24 Thread Rodrigo Campos
Package: pulseaudio
Version: 7.1-2
Severity: normal

Dear Maintainer,

I'be updated debian testing (didn't update in a while) and after I upgraded,
sound from programs that run as a different user stopped working.

When some other user tries to run: "/usr/bin/pulseaudio --start
--log-target=syslog" it fails with errors like:

Jan 24 22:01:58 lindsay pulseaudio[10238]: [pulseaudio] main.c: 
User-configured
server at 
{d07a5e247c911a2ac8ca6d8652d822c1}unix:/run/user/1000/pulse/native,
refusing to start/autospawn.
Jan 24 22:08:13 lindsay pulseaudio[11867]: [pulseaudio] main.c: 
User-configured
server at lindsay, refusing to start/autospawn.

Both users, the user that opened the desktop environment (let's call him userA)
and the other user trying to run pulseaudio/firefox (let's call him userB) are
member of group audio. Also, userA uid is 1000 and userB uid is 1001.

Usually, as autospawn is enabled, when running firefox as userB and sound
was needed, pulseaudio was started and audio just worked. Now everything works
fine, except audio doesn't play. Probably because it fails as above when trying
to start pulseaudio.

I've found the following work-around, though, to make this work again and this
is why I'm reporting it to pulseaudio.

If userA logins to the desktop env and opens a console and as userB (I'm doing
"su - userB") runs:

pax11publish -r; /usr/bin/pulseaudio --start --log-target=syslog

then audio works again.

To check if audio works, and to be sure is nothing related to firefox, I run as
userA in the desktop env:

sudo -u userB -- aplay /usr/share/sounds/alsa/Front_Center.wav

iAfter doing the "pax11publish ..." command above, this command works. Before it
does not. And, of course, this also fixes the audio in firefox.


Please let me know if I can help you in any way



Thanks a lot,
Rodrigo



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: stretch/sid
  APT prefers testing-proposed-updates
  APT policy: (900, 'testing-proposed-updates'), (900, 'testing'), (500, 
'proposed-updates'), (500, 'stable'), (400, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages pulseaudio depends on:
ii  adduser   3.113+nmu3
ii  libasound21.0.29-1
ii  libasound2-plugins1.0.29-1
ii  libc6 2.21-6
ii  libcap2   1:2.24-12
ii  libdbus-1-3   1.10.6-1
ii  libfftw3-single3  3.3.4-2
ii  libgcc1   1:5.3.1-5
ii  libice6   2:1.0.9-1+b1
ii  libltdl7  2.4.2-1.11
ii  liborc-0.4-0  1:0.4.24-1
ii  libpulse0 7.1-2
ii  libsm62:1.2.2-1+b1
ii  libsndfile1   1.0.25-10
ii  libsoxr0  0.1.2-1
ii  libspeexdsp1  1.2~rc1.2-1
ii  libstdc++65.3.1-5
ii  libsystemd0   228-4
ii  libtdb1   1.3.8-1
ii  libudev1  228-4
ii  libwebrtc-audio-processing-0  0.1-3
ii  libx11-6  2:1.6.3-1
ii  libx11-xcb1   2:1.6.3-1
ii  libxcb1   1.11.1-1
ii  libxtst6  2:1.2.2-1+b1
ii  lsb-base  9.20160110
ii  pulseaudio-utils  7.1-2
ii  udev  228-4

Versions of packages pulseaudio recommends:
pn  pulseaudio-module-x11  
pn  rtkit  

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  3.0-3+b2
pn  pavumeter



Bug#810325: Wordpress backported patches

2016-01-08 Thread Rodrigo Campos
Or, if you prefer, you can see the changes backported to 4.1 directly by
wordpress (they release 4.1.9 that you can use as base for debian stable).

Also, if you want to see the patches in git, you can see:

https://github.com/WordPress/WordPress/commits/4.1-branch

The relevant patch that Salvatore points out, is backported there (in fact,
there are only 3 patches in this new 4.1.x release).

So, if the patch does not apply cleany, as long as wordpress maintains that
branch, you can just apply the patches from there.




Thanks a lot,
Rodrigo



Bug#806157: backupninja: Don't use "--extra-clean" with duplicity >= 0.6.20

2015-11-24 Thread Rodrigo Campos
Package: backupninja
Version: 1.0.1-2
Severity: normal

Dear Maintainer,

When running duplicity with the "--extra-clean" flag, it removes used signatures
and makes difficult to restore backups older than the last full backup, as
reported here[1].

Also, this was added to backupninja to workaround a bug in duplicity that does
not exist anymore since duplicity >=0.6.20, as you can see here[2].

And debian stable ships with duplicity > 0.6.20, so it only breaks things this
"--extra-clean" flag used in backupninja.

Please apply the patch in [2] to backupninja in stable, as it breaks the restore
of old backups for no good reason (it's just a bug). As you can see, the patch
checks for the version, so it's safe to even apply for all other versions
maintained, even if they ship with an older version of duplicity.

For my use case, jessie and testing are the most important, and in any case
those are the only ones that ship with a fixed version of duplicity.




Thanks a lot,
Rodrigo


[1]: https://lists.nongnu.org/archive/html/duplicity-talk/2015-11/msg9.html
[2]: https://labs.riseup.net/code/issues/6357



Bug#783572: New upstream release

2015-09-24 Thread Rodrigo Campos
Hi,

I'd need postfix 3.0 for full SMTPUTF8 support too. Please upgrade :)





Thanks a lot,
Rodrigo



  1   2   3   4   5   6   7   8   9   >