profile
viewpoint
Balint Reczey rbalint Hungary/Budapest https://balintreczey.hu Ubuntu Core Developer, Debian Developer, Wireshark Core Developer, etc.

microsoft/WSL-DistroLauncher 1303

Sample/reference launcher app for WSL distro Microsoft Store packages.

mvo5/unattended-upgrades 166

Automatic installation of security upgrades on apt based systems

rbalint/charva 10

Git clone of Charva's svn repository at https://sourceforge.net/p/charva/code/

rbalint/erlsvc 2

CLI to control Erlang service, see URL for details

rbalint/homebrew-gtk-quartz 1

The missing package manager for OS X.

rbalint/android_device_samsung_janice 0

Device Tree for Samsung Galaxy S Advance (GT-I9070)

rbalint/android_device_samsung_u8500-common 0

Common Files for Samsung's NovaThor U8500 based devices (Galaxy S Advance, Galaxy Ace 2 and Galaxy Beam)

rbalint/apitrace 0

Tools for tracing OpenGL, Direct3D, and other graphics APIs

rbalint/archive-auth-mirror 0

Juju charm to mirror and sync an Ubuntu repository

rbalint/autopkgtest-db-reports 0

Reports generated from Ubuntu's autopkgtest run database

PR closed norbusan/debian-xxhash

New upstream release packaging

The man pages related commit was needed to keep shipping compressed man pages, as pointed out by Lintian.

+6758 -4095

4 comments

47 changed files

rbalint

pr closed time in 7 days

pull request commentnorbusan/debian-xxhash

New upstream release packaging

I've uploaded and orphaned the package, thanks! https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003524

rbalint

comment created time in 7 days

PR closed norbusan/debian-xxhash

New upstream version 0.8.1
+6735 -4075

0 comment

40 changed files

rbalint

pr closed time in 7 days

pull request commentnorbusan/debian-xxhash

New upstream release packaging

Giving it a bit more thought I'll go with the NMU version as you asked for.

rbalint

comment created time in 7 days

pull request commentnorbusan/debian-xxhash

New upstream release packaging

Yes I know about that, I'm sorry and I understand that you don't want to continue maintaining the package. If you allow me I move the packaging repo to salsa, uploade the package with a normal version and perform the orphaning after that. Thank you for your work!

rbalint

comment created time in 7 days

PR opened norbusan/debian-xxhash

New upstream release packaging

The man pages related commit was needed to keep shipping compressed man pages, as pointed out by Lintian.

+6758 -4095

0 comment

47 changed files

pr created time in 7 days

PR opened norbusan/debian-xxhash

New upstream version 0.8.1
+6735 -4075

0 comment

40 changed files

pr created time in 7 days

push eventrbalint/debian-xxhash

Balint Reczey

commit sha a78856ab21c4b641540b69d0d504dccbb7e35112

Update symbols

view details

Balint Reczey

commit sha 674f20ca092462a31072d474ccf7edcc177d3da3

Rework shipping man pages

view details

Balint Reczey

commit sha 615403928315c3a3b0128971d2b271c097fb03c0

Update changelog

view details

push time in 7 days

push eventrbalint/debian-xxhash

Balint Reczey

commit sha 140602b6b9106dde521579b06222eb53db673d92

New upstream version 0.8.1

view details

push time in 8 days

created tagrbalint/debian-xxhash

tagupstream/0.8.1

created time in 8 days

push eventrbalint/debian-xxhash

Balint Reczey

commit sha 9f33b484ef169187318f6ad882da024c27ee7c93

pristine-tar data for xxhash_0.8.1.orig.tar.gz

view details

push time in 8 days

push eventrbalint/debian-xxhash

Balint Reczey

commit sha 140602b6b9106dde521579b06222eb53db673d92

New upstream version 0.8.1

view details

Balint Reczey

commit sha 03e80d3d66a717b0ccb2b0a718f032348de5e956

Update upstream source from tag 'upstream/0.8.1' Update to upstream version '0.8.1' with Debian dir 03746cced5345d6e1d8c10cd946ab75bd94093e6

view details

Balint Reczey

commit sha 535b5cac96c92a3254aa7ab7bff9cd7d63c6f0fd

Drop upstream-b4dbf5fefc37b8a-fix-empty-version-in-pc-file patch It is included in the new upstream release

view details

Balint Reczey

commit sha 57eb04f85d1cdc29099862900d697af132511c66

Update changelog

view details

Balint Reczey

commit sha 11f9b2f070164180506da87d5c72397d01d41569

Update symbols

view details

Balint Reczey

commit sha c28aa8203ac70bc342f7c86de21e9de9893e1212

Ship compressed man pages

view details

push time in 8 days

pull request commentmvo5/unattended-upgrades

Fix adjusting candidates

@flamein I'm not working on this project for the foreseeable future: https://github.com/mvo5/unattended-upgrades/pull/308 I suggest trying to get Foundation Team's attention to the Launchpad bug to get it backported.

rbalint

comment created time in 11 days

delete branch rbalint/unattended-upgrades

delete branch : fix-adjusting-candidates

delete time in 11 days

Pull request review commentshadow-maint/shadow

[wip] update licensing info

-NOTE:-  This license has been obsoleted by the change to the BSD-style copyright.-  You may continue to use this license if you wish, but you are under no-  obligation to do so.--(*-This document is freely plagiarised from the 'Artistic Licence',-distributed as part of the Perl v4.0 kit by Larry Wall, which is-available from most major archive sites.  I stole it from CrackLib.--	$Id$-*)--This documents purpose is to state the conditions under which this-Package (See definition below) viz: "Shadow", the Shadow Password Suite-which is held by Julianne Frances Haugh, may be copied, such that the-copyright holder maintains some semblance of artistic control over the-development of the package, while giving the users of the package the-right to use and distribute the Package in a more-or-less customary-fashion, plus the right to make reasonable modifications.--So there.--***************************************************************************--Definitions:---A "Package" refers to the collection of files distributed by the-Copyright Holder, and derivatives of that collection of files created-through textual modification, or segments thereof.--"Standard Version" refers to such a Package if it has not been modified,-or has been modified in accordance with the wishes of the Copyright-Holder.--"Copyright Holder" is whoever is named in the copyright or copyrights-for the package.--"You" is you, if you're thinking about copying or distributing this-Package.--"Reasonable copying fee" is whatever you can justify on the basis of-media cost, duplication charges, time of people involved, and so on.-(You will not be required to justify it to the Copyright Holder, but-only to the computing community at large as a market that must bear the-fee.)--"Freely Available" means that no fee is charged for the item itself,-though there may be fees involved in handling the item.  It also means-that recipients of the item may redistribute it under the same-conditions they received it.---1.  You may make and give away verbatim copies of the source form of the-Standard Version of this Package without restriction, provided that you-duplicate all of the original copyright notices and associated-disclaimers.--2.  You may apply bug fixes, portability fixes and other modifications-derived from the Public Domain or from the Copyright Holder.  A Package-modified in such a way shall still be considered the Standard Version.--3.  You may otherwise modify your copy of this Package in any way,-provided that you insert a prominent notice in each changed file stating-how and when AND WHY you changed that file, and provided that you do at-least ONE of the following:--a) place your modifications in the Public Domain or otherwise make them-Freely Available, such as by posting said modifications to Usenet or an-equivalent medium, or placing the modifications on a major archive site-such as uunet.uu.net, or by allowing the Copyright Holder to include-your modifications in the Standard Version of the Package.--b) use the modified Package only within your corporation or organization.--c) rename any non-standard executables so the names do not conflict with-standard executables, which must also be provided, and provide separate-documentation for each non-standard executable that clearly documents-how it differs from the Standard Version.--d) make other distribution arrangements with the Copyright Holder.--4.  You may distribute the programs of this Package in object code or-executable form, provided that you do at least ONE of the following:--a) distribute a Standard Version of the executables and library files,-together with instructions (in the manual page or equivalent) on where-to get the Standard Version.--b) accompany the distribution with the machine-readable source of the-Package with your modifications.--c) accompany any non-standard executables with their corresponding-Standard Version executables, giving the non-standard executables-non-standard names, and clearly documenting the differences in manual-pages (or equivalent), together with instructions on where to get the-Standard Version.--d) make other distribution arrangements with the Copyright Holder.--5.  You may charge a reasonable copying fee for any distribution of this-Package.  You may charge any fee you choose for support of this Package.-YOU MAY NOT CHARGE A FEE FOR THIS PACKAGE ITSELF.  However, you may-distribute this Package in aggregate with other (possibly commercial)-programs as part of a larger (possibly commercial) software distribution-provided that YOU DO NOT ADVERTISE this package as a product of your-own.--6.  The name of the Copyright Holder may not be used to endorse or-promote products derived from this software without specific prior-written permission.--7.  THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED-WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF-MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.--				The End+SPDX-License-Identifier: BSD-3-Clause

@andrewshadura I agree that the project is belived to be BSD licensed, but looking at the current state the release tarballs can't be distributed under BSD. If we remove atudel the resulting tarball can be distributed under GPL, but not under BSD (3 clause), because it contains a GPL licensed source file. If we cut vipw.c, the remaining tarball can be distributed under BSD (3 clause). From Debian's perspective I'm OK with keeping vipw.c in the tarball, but I have to exclude atudel, for sure, to keep shadow's source in main. It could be claimed, that atudel and vipw.c are only bundled, but this needs an explanation in the COPYING file, IMO.

hallyn

comment created time in a month

PullRequestReviewEvent

Pull request review commentshadow-maint/shadow

[wip] update licensing info

-NOTE:-  This license has been obsoleted by the change to the BSD-style copyright.-  You may continue to use this license if you wish, but you are under no-  obligation to do so.--(*-This document is freely plagiarised from the 'Artistic Licence',-distributed as part of the Perl v4.0 kit by Larry Wall, which is-available from most major archive sites.  I stole it from CrackLib.--	$Id$-*)--This documents purpose is to state the conditions under which this-Package (See definition below) viz: "Shadow", the Shadow Password Suite-which is held by Julianne Frances Haugh, may be copied, such that the-copyright holder maintains some semblance of artistic control over the-development of the package, while giving the users of the package the-right to use and distribute the Package in a more-or-less customary-fashion, plus the right to make reasonable modifications.--So there.--***************************************************************************--Definitions:---A "Package" refers to the collection of files distributed by the-Copyright Holder, and derivatives of that collection of files created-through textual modification, or segments thereof.--"Standard Version" refers to such a Package if it has not been modified,-or has been modified in accordance with the wishes of the Copyright-Holder.--"Copyright Holder" is whoever is named in the copyright or copyrights-for the package.--"You" is you, if you're thinking about copying or distributing this-Package.--"Reasonable copying fee" is whatever you can justify on the basis of-media cost, duplication charges, time of people involved, and so on.-(You will not be required to justify it to the Copyright Holder, but-only to the computing community at large as a market that must bear the-fee.)--"Freely Available" means that no fee is charged for the item itself,-though there may be fees involved in handling the item.  It also means-that recipients of the item may redistribute it under the same-conditions they received it.---1.  You may make and give away verbatim copies of the source form of the-Standard Version of this Package without restriction, provided that you-duplicate all of the original copyright notices and associated-disclaimers.--2.  You may apply bug fixes, portability fixes and other modifications-derived from the Public Domain or from the Copyright Holder.  A Package-modified in such a way shall still be considered the Standard Version.--3.  You may otherwise modify your copy of this Package in any way,-provided that you insert a prominent notice in each changed file stating-how and when AND WHY you changed that file, and provided that you do at-least ONE of the following:--a) place your modifications in the Public Domain or otherwise make them-Freely Available, such as by posting said modifications to Usenet or an-equivalent medium, or placing the modifications on a major archive site-such as uunet.uu.net, or by allowing the Copyright Holder to include-your modifications in the Standard Version of the Package.--b) use the modified Package only within your corporation or organization.--c) rename any non-standard executables so the names do not conflict with-standard executables, which must also be provided, and provide separate-documentation for each non-standard executable that clearly documents-how it differs from the Standard Version.--d) make other distribution arrangements with the Copyright Holder.--4.  You may distribute the programs of this Package in object code or-executable form, provided that you do at least ONE of the following:--a) distribute a Standard Version of the executables and library files,-together with instructions (in the manual page or equivalent) on where-to get the Standard Version.--b) accompany the distribution with the machine-readable source of the-Package with your modifications.--c) accompany any non-standard executables with their corresponding-Standard Version executables, giving the non-standard executables-non-standard names, and clearly documenting the differences in manual-pages (or equivalent), together with instructions on where to get the-Standard Version.--d) make other distribution arrangements with the Copyright Holder.--5.  You may charge a reasonable copying fee for any distribution of this-Package.  You may charge any fee you choose for support of this Package.-YOU MAY NOT CHARGE A FEE FOR THIS PACKAGE ITSELF.  However, you may-distribute this Package in aggregate with other (possibly commercial)-programs as part of a larger (possibly commercial) software distribution-provided that YOU DO NOT ADVERTISE this package as a product of your-own.--6.  The name of the Copyright Holder may not be used to endorse or-promote products derived from this software without specific prior-written permission.--7.  THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED-WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF-MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.--				The End+SPDX-License-Identifier: BSD-3-Clause

@andrewshadura Do you have some links? I guess you question the GPL as the whole project's license and not the problem with atudel.

hallyn

comment created time in a month

PullRequestReviewEvent

Pull request review commentshadow-maint/shadow

[wip] update licensing info

-NOTE:-  This license has been obsoleted by the change to the BSD-style copyright.-  You may continue to use this license if you wish, but you are under no-  obligation to do so.--(*-This document is freely plagiarised from the 'Artistic Licence',-distributed as part of the Perl v4.0 kit by Larry Wall, which is-available from most major archive sites.  I stole it from CrackLib.--	$Id$-*)--This documents purpose is to state the conditions under which this-Package (See definition below) viz: "Shadow", the Shadow Password Suite-which is held by Julianne Frances Haugh, may be copied, such that the-copyright holder maintains some semblance of artistic control over the-development of the package, while giving the users of the package the-right to use and distribute the Package in a more-or-less customary-fashion, plus the right to make reasonable modifications.--So there.--***************************************************************************--Definitions:---A "Package" refers to the collection of files distributed by the-Copyright Holder, and derivatives of that collection of files created-through textual modification, or segments thereof.--"Standard Version" refers to such a Package if it has not been modified,-or has been modified in accordance with the wishes of the Copyright-Holder.--"Copyright Holder" is whoever is named in the copyright or copyrights-for the package.--"You" is you, if you're thinking about copying or distributing this-Package.--"Reasonable copying fee" is whatever you can justify on the basis of-media cost, duplication charges, time of people involved, and so on.-(You will not be required to justify it to the Copyright Holder, but-only to the computing community at large as a market that must bear the-fee.)--"Freely Available" means that no fee is charged for the item itself,-though there may be fees involved in handling the item.  It also means-that recipients of the item may redistribute it under the same-conditions they received it.---1.  You may make and give away verbatim copies of the source form of the-Standard Version of this Package without restriction, provided that you-duplicate all of the original copyright notices and associated-disclaimers.--2.  You may apply bug fixes, portability fixes and other modifications-derived from the Public Domain or from the Copyright Holder.  A Package-modified in such a way shall still be considered the Standard Version.--3.  You may otherwise modify your copy of this Package in any way,-provided that you insert a prominent notice in each changed file stating-how and when AND WHY you changed that file, and provided that you do at-least ONE of the following:--a) place your modifications in the Public Domain or otherwise make them-Freely Available, such as by posting said modifications to Usenet or an-equivalent medium, or placing the modifications on a major archive site-such as uunet.uu.net, or by allowing the Copyright Holder to include-your modifications in the Standard Version of the Package.--b) use the modified Package only within your corporation or organization.--c) rename any non-standard executables so the names do not conflict with-standard executables, which must also be provided, and provide separate-documentation for each non-standard executable that clearly documents-how it differs from the Standard Version.--d) make other distribution arrangements with the Copyright Holder.--4.  You may distribute the programs of this Package in object code or-executable form, provided that you do at least ONE of the following:--a) distribute a Standard Version of the executables and library files,-together with instructions (in the manual page or equivalent) on where-to get the Standard Version.--b) accompany the distribution with the machine-readable source of the-Package with your modifications.--c) accompany any non-standard executables with their corresponding-Standard Version executables, giving the non-standard executables-non-standard names, and clearly documenting the differences in manual-pages (or equivalent), together with instructions on where to get the-Standard Version.--d) make other distribution arrangements with the Copyright Holder.--5.  You may charge a reasonable copying fee for any distribution of this-Package.  You may charge any fee you choose for support of this Package.-YOU MAY NOT CHARGE A FEE FOR THIS PACKAGE ITSELF.  However, you may-distribute this Package in aggregate with other (possibly commercial)-programs as part of a larger (possibly commercial) software distribution-provided that YOU DO NOT ADVERTISE this package as a product of your-own.--6.  The name of the Copyright Holder may not be used to endorse or-promote products derived from this software without specific prior-written permission.--7.  THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED-WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF-MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.--				The End+SPDX-License-Identifier: BSD-3-Clause

I think BSD-3-Clause is not a valid license for the whole project. I think there is none, since contrib/atudel is BSD-4-Clause which is not compatible with GPL https://en.wikipedia.org/wiki/BSD_licenses#4-clause_license_(original_%22BSD_License%22), yet src/vipw.c is licensed under GPL. I suggest dropping contrib/atudel or splitting it out to a separate project.

If vipw.c stays in the source under GPL, then the the license of the project should be GPL (with BSD parts).

hallyn

comment created time in a month

Pull request review commentshadow-maint/shadow

[wip] update licensing info

-NOTE:-  This license has been obsoleted by the change to the BSD-style copyright.-  You may continue to use this license if you wish, but you are under no-  obligation to do so.--(*-This document is freely plagiarised from the 'Artistic Licence',-distributed as part of the Perl v4.0 kit by Larry Wall, which is-available from most major archive sites.  I stole it from CrackLib.--	$Id$-*)--This documents purpose is to state the conditions under which this-Package (See definition below) viz: "Shadow", the Shadow Password Suite-which is held by Julianne Frances Haugh, may be copied, such that the-copyright holder maintains some semblance of artistic control over the-development of the package, while giving the users of the package the-right to use and distribute the Package in a more-or-less customary-fashion, plus the right to make reasonable modifications.--So there.--***************************************************************************--Definitions:---A "Package" refers to the collection of files distributed by the-Copyright Holder, and derivatives of that collection of files created-through textual modification, or segments thereof.--"Standard Version" refers to such a Package if it has not been modified,-or has been modified in accordance with the wishes of the Copyright-Holder.--"Copyright Holder" is whoever is named in the copyright or copyrights-for the package.--"You" is you, if you're thinking about copying or distributing this-Package.--"Reasonable copying fee" is whatever you can justify on the basis of-media cost, duplication charges, time of people involved, and so on.-(You will not be required to justify it to the Copyright Holder, but-only to the computing community at large as a market that must bear the-fee.)--"Freely Available" means that no fee is charged for the item itself,-though there may be fees involved in handling the item.  It also means-that recipients of the item may redistribute it under the same-conditions they received it.---1.  You may make and give away verbatim copies of the source form of the-Standard Version of this Package without restriction, provided that you-duplicate all of the original copyright notices and associated-disclaimers.--2.  You may apply bug fixes, portability fixes and other modifications-derived from the Public Domain or from the Copyright Holder.  A Package-modified in such a way shall still be considered the Standard Version.--3.  You may otherwise modify your copy of this Package in any way,-provided that you insert a prominent notice in each changed file stating-how and when AND WHY you changed that file, and provided that you do at-least ONE of the following:--a) place your modifications in the Public Domain or otherwise make them-Freely Available, such as by posting said modifications to Usenet or an-equivalent medium, or placing the modifications on a major archive site-such as uunet.uu.net, or by allowing the Copyright Holder to include-your modifications in the Standard Version of the Package.--b) use the modified Package only within your corporation or organization.--c) rename any non-standard executables so the names do not conflict with-standard executables, which must also be provided, and provide separate-documentation for each non-standard executable that clearly documents-how it differs from the Standard Version.--d) make other distribution arrangements with the Copyright Holder.--4.  You may distribute the programs of this Package in object code or-executable form, provided that you do at least ONE of the following:--a) distribute a Standard Version of the executables and library files,-together with instructions (in the manual page or equivalent) on where-to get the Standard Version.--b) accompany the distribution with the machine-readable source of the-Package with your modifications.--c) accompany any non-standard executables with their corresponding-Standard Version executables, giving the non-standard executables-non-standard names, and clearly documenting the differences in manual-pages (or equivalent), together with instructions on where to get the-Standard Version.--d) make other distribution arrangements with the Copyright Holder.--5.  You may charge a reasonable copying fee for any distribution of this-Package.  You may charge any fee you choose for support of this Package.-YOU MAY NOT CHARGE A FEE FOR THIS PACKAGE ITSELF.  However, you may-distribute this Package in aggregate with other (possibly commercial)-programs as part of a larger (possibly commercial) software distribution-provided that YOU DO NOT ADVERTISE this package as a product of your-own.--6.  The name of the Copyright Holder may not be used to endorse or-promote products derived from this software without specific prior-written permission.--7.  THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED-WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF-MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.--				The End+SPDX-License-Identifier: BSD-3-Clause++All files under this project either++1. fall under the BSD 3 clause license (by default).++2. carry an SBDX header declaring what license applies.

SPDX

hallyn

comment created time in a month

PullRequestReviewEvent
PullRequestReviewEvent

pull request commentshadow-maint/shadow

[wip] update licensing info

I'm waiting with the Debian upload until this licensing change lands (and ideally gets in a release).

hallyn

comment created time in a month

pull request commentshadow-maint/shadow

libsubid/api.c: make Prog not static

@hallyn please finish the fix #444 instead. This is still ugly. :-(

hallyn

comment created time in a month

pull request commentshadow-maint/shadow

2021 11 27/libsubid symbols

I have not seen this anywhere

there are a bunch of .*_ABI_VERSION definitions under /usr/include.

Said so, if it looks redundant, I will find some other way to deal with the renaming.

I'm sorry, you are righ and I did not get what you meant. I suggest setting not only the major version, but minor and micro to be able to check for it like it is done for glib: GLIB_CHECK_VERSION(2, 68, 0).

hallyn

comment created time in 2 months

issue commentshadow-maint/shadow

Licensing

Next shadow will need an FTP Master review due to the addition of the new library. The review will include reviewing the license and if re-licensing takes place I'd appreciate if that could happen before releasing 4.10. Otherwise I have to revisit every file for the proper license and update https://salsa.debian.org/rbalint/shadow/-/blob/master/debian/copyright just to update it again. :-(

DavidKCalnex

comment created time in 2 months

pull request commentshadow-maint/shadow

2021 11 27/libsubid symbols

Ok, thanks. So perhaps I could add them as aliases for now, with the intent of removing the old names "eventually"?

sure thanks, that would help.

Thinking more of it: would it be possible to export the ABI major number as part of subid.h? In this way, I could address the problem directly in the Cgo code with some macros (not sure if there is a smarter way in Go to have the equivalent of AC_CHECK_FUNCS) so you won't have to worry about carrying the alias. What do you think?

This is redundant and I have not seen this anywhere. I'm sure there is something in Go that helps with major shared library version bumps. If you need something at run time, you can certainly use dlsym from Go.

hallyn

comment created time in 2 months

more