the
Debian bug report policies, but I got worried that the GDM3 3.8.4.4 will be
in Debian Jessie in a couple of days, without really solving the bug.
--
Samuel Henrique O. P. [samueloph]
Técnico em Informática - UTFPR [2012].
Estudante de Engenharia de Computação - UTFPR.
>
> I'm not sure if this really should be the case, even if another init
> system is used, but then it works at least with systemd.
>
> Best regards,
> Andreas
>
--
Samuel Henrique O. P. [samueloph]
Técnico em Informática - UTFPR [2012].
Estudante de Engenharia de Computação - UTFPR.
t the upstream versions has this
problem fixed, also, why have we an outdated version o telepathy-idle? Even
in SID repo.
--
Samuel Henrique O. P. [samueloph]
Técnico em Informática - UTFPR [2012].
Estudante de Engenharia de Computação - UTFPR.
[1].
[1]https://anonscm.debian.org/gitweb/?p=collab-maint/iptraf-ng.git
Samuel Henrique
, i can help with the fix, given the maintainers permission to do so.
[1]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842355
Samuel Henrique
g,
which should be accepted without trouble considering the case.
Of course, that is if you don't prefer to do it yourself, please feel free
to ask for help on any stage.
Thanks for the quick reply :)
Samuel Henrique
2017-03-21 10:02 GMT-03:00 Aron Xu :
> On Tue, Mar 21, 2017 at 3:43 PM
-ng/+bug/1502593
and
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746014
Samuel Henrique
Hello everyone,
Holger, i think you may remember me from debconf, i already pushed some
changes on another branch on anarchism's git (as you suggested), i just
need your sponsor (and to add this change there before your sponsor, which
i'll do today, soon).
Thanks
Samuel Henrique
201
r the help.
Samuel Henrique
would appreciate a lot if you could give me DM rights on the package
too so i won't need a sponsor next time (i will apply for DD as soon as i
get someone to advocate me).
Thanks Holger :)
Samuel Henrique
the package, so in the future i won't need sponsorship for bwm-ng (i also
want to apply for DD as soon as i got someone to advocate me, i will try to
work hard to achieve it this year)
Samuel Henrique
l free to contact me.
I asked to join the python team, but got no response, that's why i decided
to package it on collab under my maintenance, although i should probably
just directly contact some active member of the python team.
[1]https://anonscm.debian.org/git/collab-maint/python-pluginb
t.cgi?bug=826982
Samuel Henrique
gt;
>
I'm a DM for almost 1 year now :)
BTW, i pushed some last changes and now we have proper d/watch support, i
also updated the watch wiki at d.o to fix the gitlab example :)
The only thing missing is now is that you're having problems building
15.1-1, if i understood correctly.
Em 11/09/2017 09:24, "Holger Levsen" escreveu:
On Sun, Sep 10, 2017 at 11:37:34AM -0300, Samuel Henrique wrote:
> a.) I don't know how to build this with git-buildpackage, can you please
> > explain?
> I'm not sure i understood your problem, gbp buildpackage
2017-09-11 12:34 GMT-03:00 Holger Levsen :
> On Mon, Sep 11, 2017 at 12:30:56PM -0300, Samuel Henrique wrote:
> > I run gbp buildpackage on master, my gbp is configured to run sbuild
> using
> > sid, just like the sbuild wiki page suggests, I'm using buster.
>
> oh,
All solved, package is on mentors Holger :)
thanks
Samuel Henrique
Package: t50
Version: 5.6.15-1
Severity: grave
Upstream removed patch which accepted flags passed to compiler and now it uses
-march=native.
I'm one of the maintainers of t50 and i'm opening this bug to aware those who
wish to update t50 from unstable.
I will fix this in 2 days max (there's a cha
(possibly wrongly)
created that folder?
my bet is that this was not created by jwm or its package.
thanks
Samuel Henrique
Oops, i replied to the wrong bugreport, sorry, it was meant to this one[1].
[1]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849534
Samuel Henrique
2017-07-31 20:32 GMT-03:00 Samuel Henrique :
> Hello Ulyanich,
>
> thanks for reporting this, and sorry for taking so long to rep
(possibly wrongly)
created that folder?
my bet is that this was not created by jwm or its package.
thanks
Samuel Henrique
Hi Holger,
I bet you'll like these patches[1], it's your pick, let me now and i can
patch on my [debian] side so we have reproducible hoichess builds before
you make a new release.
[1]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847768
Samuel Henrique
Package: wnpp
Owner: "Samuel Henrique Oltramari Pinto (SamuelOPH)"
Severity: wishlist
* Package name: hashid
Version : 3.1.4
Upstream Author : c0re
* URL : https://psypanda.github.io/hashID/
* License : GPL-3+
Programming Lang: Python
D
ee if the build becomes reproducible or ask
someone for help to at least have confirmation that the other name won't be
a problem.
Thanks a lot for your help!
[1]
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/kdbg.html
Samuel Henrique O. P. [samueloph]
teful :)
Also, i believe you can also send this upstream, but if you don't, i can do
that for you.
Samuel Henrique
Control: tag -1 + pending
Fix commited to git, version 20130526-2 will fix/close this bug.
Thanks for the patch!
Samuel Henrique
Hello Giovani,
Did you give a look a this one?
I think we could enable xattr on experimental and see if it breaks build on
the other architectures (actually, other kernels).
I can do that if you want.
Samuel Henrique
Hello Michael,
Have you seen this bugreport?
I think we should change guymager to Architecture: any and see in which
architectures it doesn't builds.
I can prepare an upload to experimental for test purposes if you want.
Regards,
Samuel Henrique
Control: tag -1 + pending
Fix commited.
Samuel Henrique
Control: tags -1 + pending
Control: forwarded -1 https://github.com/aircrack-ng/aircrack-ng/pull/91
Fix commited and sent upstream, thanks a lot Reiner
Samuel Henrique
Hi all,
I'm interested in maintaining openxenmanager, however the package is very
outdated and it needs some work to get in shape, i wouldn't like to
maintain it alone, if there's someone willing to work together on this,
please reply here.
Samuel Henrique
thanks for warning me.
Samuel Henrique
ackage/mtr
[2]:https://anonscm.debian.org/git/collab-maint/mtr.git
Samuel Henrique
Hi Reiner,
Could you please follow up the discussion at[1]?
I added you as a collaborator on my fork, so what you push there will
update on the PR (check your email for a github collab. invite)
[1]https://github.com/aircrack-ng/aircrack-ng/pull/91
Samuel Henrique
2016-12-25 18:13 GMT-02:00
Hi Robert,
Did you have a look at this one?
I'm in favor of using dh_auto_configure, just would like to check with you
if i'm missing something (like a regression).
Samuel Henrique
Package: wnpp
Owner: "Samuel Henrique"
Severity: wishlist
* Package name: mdk3
Version : 6.0
Upstream Author : Pedro Larbig "ASPj"
* URL : http://aspj.aircrack-ng.org/#mdk3
<https://github.com/wiire/pixiewps>
* License : GP
feel free to send replies or patches.
Samuel Henrique O. P. [samueloph]
upstream and would be greatly appreciated.
[1]
https://github.com/nickg/xcowsay/blob/801653aa77824b28e9541e242badc02cc3da1cc7/xcowsay.6#L190-L193
[2]
https://github.com/nickg/xcowsay/blob/801653aa77824b28e9541e242badc02cc3da1cc7/ChangeLog#L41-L44
Samuel Henrique O. P. [samueloph]
Hi Alexandre,
Thanks for your bug report, i just confirmed that this affects 1.3 and i
forwarded to upstream.
Samuel Henrique
Hi Alexis,
As you probably already has seen, i uploaded kdbg to experimental and we
still have reproducibility problems.
https://tests.reproducible-builds.org/debian/rb-pkg/experimental/amd64/diffoscope-results/kdbg.html
Samuel Henrique
Hi all,
Thanks for the head up Gianfanco, I'll commit this patch to git within the
next hours and then ask for sponsorship.
Also, thanks a lot for the patch Reiner, you're always saving the
reproducibility of the packages i work with :)
Regards
Samuel Henrique
2016-09-09 4:46
Package: wnpp
Owner: "Samuel Henrique"
Severity: wishlist
* Package name: wafw00f
Version : 0.9.4
Upstream Author : Sandro Gauci >
* URL : https://github.com/EnableSecurity/wafw00f
<https://psypanda.github.io/hashID/>
* License : BSD-3-c
.
[Logan Rosen]
* Bump DH level to 9 (closes: #829745).
* debian/rules:
- Remove legacy DH_COMPAT export.
- Add recommended build-arch and build-indep targets.
- Use dh_prep instead of dh_clean -k.
* debian/control:
- Depend on ${misc:Depends}.
[Samuel Henrique]
* Bump
i
would be glad to include it on the next revision (i'm currently doing a new
one and i'm willing to wait until this reproducibility problem is fixed to
upload).
Thanks.
Samuel Henrique O. P. [samueloph]
oved it :)
I updated the patch to use the new SOURCE_DATE_EPOCH variable and
> noticed another issue related to file ordering (which we didn't detect
> at the time this bug was submitted), which it also fixes.
>
Thanks, it looks ok here.
Samuel Henrique O. P. [samueloph]
201
MIT [Expat]), the next releases should be
packaged by me as soon as they're released unless big changes to the
packaging are needed.
I should upload the new version today on mentors, but i believe it will
take some days until reaching unstable (i have to wait for a sponsor, as
i'm not a D
Hi Hugo,
I've just created the git repo. and pushed hashid, i didn't push any tags
because i believe we will only tag hashid when we update the manpage, if i
did something wrong please feel free to point out.
Thanks.
Samuel Henrique O. P. [samueloph]
2016-08-20 17:19 GMT-03:00 Hug
ing them too, some days ago i did see
something about building a reproducible build environment too, what i
believe it would be nice to have in our team's package (reproducibility).
I'm very grateful for you taking your time to review my changes and
reporting problems with a nice explanation attached, thanks.
[1]https://wiki.debian.org/Teams/pkg-security
Samuel Henrique O. P. [samueloph]
Package: wnpp
Owner: "Samuel Henrique"
Severity: wishlist
* Package name: pixiewps
Version : 1.2.2
Upstream Author : wi7ire
* URL : https://github.com/wiire/pixiewps
* License : GPL-3+ and Apache-2.0
Programming Lang: C
Description : O
nsored. I just didn't wanna do this without asking you, because you may
want to do a package upload yourself, finding a sponsor.
Either way i will be glad to help.
Thanks.
Samuel Henrique O. P. [samueloph]
mple: v1.8.1, as a result debian
is not identifying some of the project releases, including the last one
(1.8.1).
This fix is very trivial, as you can see in the patch.
Please let me know if you have any further considerations about this.
Samuel Henrique O. P. [samueloph]
From e25f459ac56a98ba3fd
ht have a removal date set).
And noticed just now: both curl and nmap's debci results are not
up-to-date on tracker.
[0] https://tracker.debian.org/pkg/grequests
[1] https://tracker.debian.org/pkg/nmap
[2] https://tracker.debian.org/pkg/licenseutils
[3] https://tracker.debian.org/pkg/dd-opentracing-cpp
I believe there's something wrong with tracker's interface.
Cheers,
--
Samuel Henrique
5-manager as I didn't catch it
when doing the initial search for rdeps, the change will be simple for
this package due to it already accepting other backends through
"libcurl-dev".
This is only a matter of changing the prefered one and getting a build
that links against something o
rl drops the nss packages.
The first option is better for me as the dependency can be removed
earlier and it will be less work for me, but number 2 doesn't require
any actions from you (thus why this bug is being cut late).
What would be your preferred option?
Thank you,
--
Samuel Henrique
rl drops the nss packages.
The first option is better for me as the dependency can be removed
earlier and it will be less work for me, but number 2 doesn't require
any actions from you (thus why this bug is being cut late).
What would be your preferred option?
Thank you,
--
Samuel Henrique
rl drops the nss packages.
The first option is better for me as the dependency can be removed
earlier and it will be less work for me, but number 2 doesn't require
any actions from you (thus why this bug is being cut late).
What would be your preferred option?
Thank you,
--
Samuel Henrique
upload it within a week (depending on how we end up coordinating
the uploads for the next changes).
[0] To be clear, I was never a fan of that, but so far I haven't seem any
practical impact.
Cheers,
--
Samuel Henrique
r the trixie release.
Cheers,
[0] https://subdivi.de/~helmut/dep17.html
[1] https://salsa.debian.org/bottoms/pkg-airspy-host/-/merge_requests/3
--
Samuel Henrique
>From 88072b72a2a756df85f6760913363af2d23d8272 Mon Sep 17 00:00:00 2001
From: Samuel Henrique
Date: Fri, 24 Nov 2023 16:13:38 +
ther information see:
[0] https://security-tracker.debian.org/tracker/CVE-2023-45853
https://www.cve.org/CVERecord?id=CVE-2023-45853
Please adjust the affected versions in the BTS as needed.
Cheers,
--
Samuel Henrique
ther information see:
[0] https://security-tracker.debian.org/tracker/CVE-2023-45853
https://www.cve.org/CVERecord?id=CVE-2023-45853
Please adjust the affected versions in the BTS as needed.
Cheers,
--
Samuel Henrique
k/-/commit/fc6e9929b1018d411df599a68d5898e42bfe6560
The commit description does not mention what/why the changes are being made,
for example, why the change from dh_auto_install to dh_install.
Cheers,
[0] https://packages.debian.org/trixie/all/sherlock/filelist
--
Samuel Henrique
but none of the API / features, then it is not
> a correct solution.
They do not share the same API.
> These descriptions do not sound related at all. In this case,
> Conflicts/Replaces is not appropriate.
I see your point now, it seems like it should be just "Conflicts", do you
agree? None of those 2 packages can/should be renamed.
Cheers,
--
Samuel Henrique
ner at #1071754.
If you agree, I can fill in the request (unless you prefer to do it yourself).
Cheers,
--
Samuel Henrique
r intention is to provide a library for
sherlock, as we've had since the package was introduced.
> Therefore, this bug can be closed, and there's IMO nothing more to do in
> the python-sherlock (the cluster lock package), as the conflict is now
> solved.
I'll reopen 1072733 since the clash still exists.
Cheers,
--
Samuel Henrique
Hello Thomas,
On Mon, 10 Jun 2024 at 12:03, Thomas Goirand wrote:
>
> On 6/9/24 18:47, Samuel Henrique wrote:
> > Zigo,
> >> I just saw that sherlock (the social networks package) moved its python
> >> files to /usr/share, instead of /usr/lib/python3/dist-pac
atchett
> content-type: text/plain
> date: Sat, 11 May 2024 19:33:28 GMT
> server: Apache
>
> curl: (92) HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1)
I get both the payload and the error.
Regards
--
Samuel Henrique
Hello Sakirnth,
> I am good and I hope you too.
All good on my side too :)
> On 4/29/24 22:24, Samuel Henrique wrote:
> > So maybe it even makes sense to get the latest releases for the transition.
>
> I agree. I normaly do both nghttp3 and ngtcp2 the same time, therefore
have a preference on not following this
approach?
Regards,
--
Samuel Henrique
Control: reopen -1 =
I see on git that the bug was closed with a Conflicts+Replaces stanza, but
that's not the correct solution for this issue.
As discussed on this bugreport, the fix is to not ship the file.
Reopening to block the problematic package to migrate to testing.
Cheers,
--
S
into other python scripts, since
it's not under dist-packages anymore.
The original proposed solution to the issue still stands: we just need to not
ship files at the root of dist-packages.
Regards,
--
Samuel Henrique
ow.
Nilson:
> As Sherlock is a private module, I moved it to usr/share according to this
> policy here:
Sherlock is not a private module.
Please proceed with importing the upstream PR to fix the issue.
Cheers,
--
Samuel Henrique
blocks elfutils, which blocks GLib,
> which will likely be blocking a significant chunk of the 64-bit time_t
> transition.
I believe this is an issue on ruby-curb and not on curl, check the following
thread on curl-library for details and possible solutions:
https://curl.se/mail/lib-2024-03/0
f you would like, we could also put the package under the curl team. We are
not a "real team" in the sense that we don't gate contributions, that's just to
make it more easy and clear that people should feel free to do team-uploads.
Regards,
--
Samuel Henrique
so we can open a feature request for any option there that's mising. I
believe it won't be an issue to revert back to GnuTLS because that's what the
package was using before the latest upload.
Regards,
--
Samuel Henrique
default backend used by curl
(the cli) for the gnutls one, so we can enable http3.
Boyuan, can you provide any details on the issues you found? Otherwise I would
recommend staying with gnutls for now and so pycurl will soon make use of a
http3-enabled libcurl.
Cheers,
--
Samuel Henrique
89cb153b782bf7be7739e3ca0bafe5a9a14c3/RELEASE-NOTES
Regards,
--
Samuel Henrique
he packaging, for now, we are
ignoring those test results).
Me and sergiodj are also currently investigating a test issue related
to ppc64el, we have got some good insights already, but would like to
fully understand what's going on and have a patch ready before
reporting. Also that issue o
(it has been more
than 10 days already) because I want to push 6 CVE fixes after this
upload. I will also request for the CVE fixes to be unblocked but I
would like this version to migrate first so it happens sooner (trying
to avoid baking this for an extra 20 days).
unblock curl/7.88.1-6
Thank you,
--
Upstream stopped providing .deb files after 0.8.3 :(
James, let me know if there's anything I can do to help packaging the
latest release, in case you have more than one package pending.
Thanks for maintaining nvim.
--
Samuel Henrique
Hello Helge,
> Please tell me if you are currently preparing a new release yourself
> and would like me to skip the NMU.
Since the package is team maintained (under the Python team), I would
prefer it if you did a team upload rather than an NMU. Honestly I
wouldn't complain if you went with an NM
easily add it then.
Sounds good, I have given you permission to push to the salsa repo.
Thanks,
--
Samuel Henrique
Control: severity -1 serious
Bumping the severity of this bug to block it from going into the next
stable release.
We should remove it from unstable as well once it's removed from testing.
I'm opening a similar bug request for adapta-kde.
Regards,
--
Samuel Henrique
it's gone from testing.
Regards,
--
Samuel Henrique
upstsream releases?
Thank you,
--
Samuel Henrique
locked by
this, as it increases the priority of fixing this.
Thank you,
[0] Since most of the reverse deps will also have to be removed, I
think the only one which stays is forensics-all.
--
Samuel Henrique
Hello Paul,
On Wed, 21 Sept 2022 at 19:58, Paul Gevers wrote:
> On 21-09-2022 20:50, Samuel Henrique wrote:
> > Please let me know if there is anything besides aircrack-ng blocked by
> > this, as it increases the priority of fixing this.
>
> Well, I pinged you because I n
been quite helpful already and I understand
we're dealing with compromises where ideally we would probably want to
have more than one version available in the repos.
Cheers,
--
Samuel Henrique
migrate to testing smoothly:
https://qa.debian.org/excuses.php?experimental=1&package=python-jsonschema
Thank you for your work :)
--
Samuel Henrique
s
decision should be done ideally before the freeze so we can take any
required actions.
Thank you,
[0] At least one issue that I've seen raised is present in all
versions of nmap we ship (since the first iteration of NPSL), which
would mean even our package in oldstable and stable is non-free.
--
Samuel Henrique
ema >= 4.10.0, so I'm opening this bug to track the
request to update python-jsonschema.
The latest release of ansible-lint as of now is 6.10.0, and it
requires jsonschema >= 4.10.0,
For reference, previous bug report asking for an update:
https://bugs.debian.org/1017629
Thank you!
--
S
I can spot
any issues.
We don't really use this bugtracker for packages in the backports
repository, so I'm not sure I can/should tag the bug as closed for
"7.87.0-1~bpo11+1", but at least we have this workaround documented
here for others.
Thanks for helping!
--
Samuel Henrique
Hello Markus,
Would you have some time to investigate this issue, please?
Thank you, (and thank you Raimon for reporting this)
--
Samuel Henrique
Hello Thomas,
Sending another ping just in case you dropped this (but still, no rush
in doing so, feel free to take your time).
On Fri, 14 Oct 2022 at 19:09, Samuel Henrique wrote:
>
> Hello Thomas, I hope you're well,
>
> Not meaning to rush you, just a heads up in case it
se CVE fixes and
the autopkgtests (coming in rev 8) in testing before asking for
8.0.1's unblock.
PS.: I've made a typo in the changelog entry where I mention "5 CVEs"
rather than 6, but it's fine since all of the 6 CVEs are listed
anyway.
unblock curl/7.88.1-7
--
Samuel
iate it if that could be done (only if that's not too much work
for the release team).
unblock curl/7.88.1-8
--
Samuel Henrique
curl_7.88.1-8.debdiff
Description: Binary data
--- libcurl4-openssl-dev_7.88.1-7_amd64.deb
+++ libcurl4-openssl-dev_7.88.1-8_amd64.deb
├── file list
│ @@ -1,3 +1,
This should be fixed by curl 7.87.0-2, which I uploaded just now.
curl BTS bug for reference: https://bugs.debian.org/1027564
Thanks,
--
Samuel Henrique
It would be really nice if there was a column for open security issues
under DDPO. I'm sure this would result in maintainers being more
proactive in fixing security issues on stable, as it's too easy to
miss them right now.
Thank you,
--
Samuel Henrique
line's
Suggests, and mention somewhere that the bindings for vim are in that
package (not sure where yet), but it's worth noting that they are two
separate projects with their own codebase each (although they look
pretty much the same).
Thank you for reporting this,
--
Samuel Henrique
as a potentially credible issue. I would gladly help
> investigate this further on, if you need so.
What did you look for when investigating this as a false positive?
Do you get the same finding when scanning the package's source code?
https://salsa.debian.org/pkg-security-team/aircrack-ng
Thank you for the report,
--
Samuel Henrique
6
PS.: You might also want to do that change on llvm-toolchain-17, but
that one does not block the migration.
Cheers,
--
Samuel Henrique
1 - 100 of 419 matches
Mail list logo
