Bug#1054086: lsm: let dh_installsystemd choose the location of units

[Lucas Castro]

Em 25/05/2024 17:42, Lucas Castro escreveu:


Em 25/05/2024 17:23, Chris Hofstaedtler escreveu:

Dear Maintainer,

On Mon, Oct 16, 2023 at 08:11:55PM +0200, Helmut Grohne wrote:

Source: lsm
Version: 1.0.4-2

I've prepared an NMU and uploaded to DELAYED/7. It is time to get
this done.

Feel free to fix this bug yourself before this time.


Chris, the bug was fixed.

There's a RFS, if I'm waiting for someone to sponsor it, if you don't 
mind, feel free to sponsorship it.


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064297


I would like the NMU be canceled.







Best,
Chris



OpenPGP_0x42F79A5E0A4D5598.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1054086: lsm: let dh_installsystemd choose the location of units

[Lucas Castro]

Em 25/05/2024 17:23, Chris Hofstaedtler escreveu:

Dear Maintainer,

On Mon, Oct 16, 2023 at 08:11:55PM +0200, Helmut Grohne wrote:

Source: lsm
Version: 1.0.4-2

I've prepared an NMU and uploaded to DELAYED/7. It is time to get
this done.

Feel free to fix this bug yourself before this time.


Chris, the bug was fixed.

There's a RFS, if I'm waiting for someone to sponsor it, if you don't 
mind, feel free to sponsorship it.


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064297




Best,
Chris



OpenPGP_0x42F79A5E0A4D5598.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1071528: ITP: hardinfo2 -- Hardinfo2 offers System Information and Benchmark for Linux Systems

[Lucas Castro]

Em 20/05/2024 22:53, xiao sheng wen(肖盛文) escreveu:

Hi,

  I had report bug #1070830[1], hardinfo package change upstream repo 
to hardinfo2

also is a better way.

IMHO, hardinfo2 only is the new version of hardinfo, it's not 
necessary to ITP a new
hardinfo2 src package in Debian. The new version has a new binary 
package named hardinfo2

is no problem.


I had mentioned that with upstream, but no response from Debian actual 
maintainer.



There's some ways to solve that.




Regard,
atzlinux

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070830

在 2024/5/20 23:01, Lucas Castro 写道:

Package: wnpp
Severity: wishlist
Owner: Lucas Castro 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name    : hardinfo2
   Version : 2.1.2
   Upstream Contact: Name 
* URL : https://hardinfo2.org/
* License : GPL-2
   Programming Lang: C
   Description : Hardinfo2 offers System Information and 
Benchmark for Linux Systems


Hardinfo2 is based on hardinfo, which have not been released >10 
years. Hardinfo2 is the reboot that was needed.


Hardinfo2 offers System Information and Benchmark for Linux Systems. 
It is able to
obtain information from both hardware and basic software. It can 
benchmark your system and compare

to other machines online.

Features include:
- Report generation (in either HTML or plain text)
- Online Benchmarking - compare your machine against other machines

Status
--
- Capabilities: Hardinfo2 currently detects most software and 
hardware detected by the OS.

- Features: Online database for exchanging benchmark results.
- Development: Currently done by contributors, hwspeedy maintains

Hardinfo2 is based on hardinfo, which have not been released >10 
years. Hardinfo2 is the reboot that was needed.







OpenPGP_0x42F79A5E0A4D5598.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1071528: ITP: hardinfo2 -- Hardinfo2 offers System Information and Benchmark for Linux Systems

[Lucas Castro]

Em 20/05/2024 16:55, Jeremy Bícha escreveu:

On Mon, May 20, 2024 at 11:09 AM Lucas Castro  wrote:

Package: wnpp
Severity: wishlist
Owner: Lucas Castro 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: hardinfo2
   Version : 2.1.2
   Upstream Contact: Name 
* URL : https://hardinfo2.org/
* License : GPL-2
   Programming Lang: C
   Description : Hardinfo2 offers System Information and Benchmark for 
Linux Systems

Hardinfo2 is based on hardinfo, which have not been released >10 years. 
Hardinfo2 is the reboot that was needed.

Hardinfo2 offers System Information and Benchmark for Linux Systems. It is able 
to
obtain information from both hardware and basic software. It can benchmark your 
system and compare
to other machines online.

Features include:
- Report generation (in either HTML or plain text)
- Online Benchmarking - compare your machine against other machines

Status
--
- Capabilities: Hardinfo2 currently detects most software and hardware detected 
by the OS.
- Features: Online database for exchanging benchmark results.
- Development: Currently done by contributors, hwspeedy maintains

Hardinfo2 is based on hardinfo, which have not been released >10 years. 
Hardinfo2 is the reboot that was needed.

Please see https://bugs.debian.org/1071373 (ITS: hardinfo) and
coordinate with Boyuan Yang on updating hardinfo.


I had talked to hardinfo maintainer but got no reply in two week or so.

I had worked with upstream to prepare the package to replace hardinfo, 
I'm just waiting for maintainer reply, if not, request sponsorship for 
package replacement.


Of course setting things on d/control.

  


Thank you,
Jeremy Bícha


Thanks,

Lucas Castro.



OpenPGP_0x42F79A5E0A4D5598.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1071528: ITP: hardinfo2 -- Hardinfo2 offers System Information and Benchmark for Linux Systems

[Lucas Castro]

Package: wnpp
Severity: wishlist
Owner: Lucas Castro 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: hardinfo2
  Version : 2.1.2
  Upstream Contact: Name 
* URL : https://hardinfo2.org/
* License : GPL-2
  Programming Lang: C
  Description : Hardinfo2 offers System Information and Benchmark for Linux 
Systems

Hardinfo2 is based on hardinfo, which have not been released >10 years. 
Hardinfo2 is the reboot that was needed.

Hardinfo2 offers System Information and Benchmark for Linux Systems. It is able 
to
obtain information from both hardware and basic software. It can benchmark your 
system and compare
to other machines online.

Features include:
- Report generation (in either HTML or plain text)
- Online Benchmarking - compare your machine against other machines

Status
--
- Capabilities: Hardinfo2 currently detects most software and hardware detected 
by the OS.
- Features: Online database for exchanging benchmark results.
- Development: Currently done by contributors, hwspeedy maintains

Hardinfo2 is based on hardinfo, which have not been released >10 years. 
Hardinfo2 is the reboot that was needed.

Bug#1064297: RFS: foolsm/1.0.21-1 -- Link connectivity monitor tool

[Lucas Castro]

Sorry for top posting.

The debian/control was modified to append Git fields, Cvs-Git and 
Cvs-Browser.


Git repository is following the DEP-14 as suggested, I really 
appreciated that workflow.


Changelog was improved. It reflects the all debian package modification 
right now.


There's something to do yet, about the gbp as Daniel had mentioned, All 
things about debian branch and upstream branch for debian git.



I had uploaded the package to mentors,

https://mentors.debian.net/debian/pool/main/l/lsm/lsm_1.0.21-1.dsc

The package can be checked from the git repository too, the following uri

Vcs-Browser: https://git.gnuabordo.com.br/foolsm.git
Vcs-Git: https://git.gnuabordo.com.br/foolsm.git

The debian/latest, debian/trixie and debian/unstable branches, all of 
them reflect debian package.


I'm maintain all those branch right now, and all of them is identical. 
I'm thinking about to delete the unstable.


I'll maintain just the debian/latest for development, debian/ for 
backports, security and propose-update and mentioned on DEP-14.



Thanks,

Lucas Castro


Em 11/05/2024 03:44, Tobias Frost escreveu:

On Mon, May 06, 2024 at 08:02:17PM +0200, Daniel Gröber wrote:

On Mon, May 06, 2024 at 02:10:53PM -0300, Lucas Castro wrote:

  [DEFAULT]
  debian-branch = gnuabordo/latest
  debian-tag = gnuabordo/%(version)s

Please let me suggest to use DEP14 for branch naming:
https://dep-team.pages.debian.net/deps/dep14/

--
tobi



OpenPGP_0x42F79A5E0A4D5598.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064297: RFS: foolsm/1.0.21-1 -- Link connectivity monitor tool

[Lucas Castro]

retitle 1064297 RFS: lsm/1.0.21-1 -- Link connectivity monitor tool


As the source package has changed the package could be retrieve by the 
following url.


The source builds the following binary packages:

  foolsm - Link connectivity monitor tool
  lsm - Link connectivity monitor tool - transitional package

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

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

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

  dget -xhttps://mentors.debian.net/debian/pool/main/l/lsm/lsm_1.0.21-1.dsc


Em 24/03/2024 16:50, Lucas Castro escreveu:


Em 23/03/2024 13:08, Tobias Frost escreveu:

Control: tags -1 moreinfo

The source package name is still being renamed, and the source package
rename is not explictly stated in the changelog.


Source package already kept old project name, only binary renamed.


I had talked about the source package rename on IRC, and no problem 
was pointed as serious then the my conclusion it wasn't going to be a 
problem.


But, by the way, it's going to be kept as it was.



(I think this renane shouldn't be done, to keep the history of the
package, not only the tracker but also the BTS and all the other
services working on source packages.)

(You should also bump the timestamp in the d/changelog, when uploading a
new package to mentors.)

Timestamp bumped.


The patch in package should be fowarded; as it only changes *comments*,
consider dropping it completly.


Dropped the patch, ASAP I'll forward to upstream.


Already uploaded to mentors.



--
tobi


Thanks Tobias.




On Thu, 14 Mar 2024 22:25:04 -0300 Lucas Castro 
wrote:

Em 06/03/2024 05:49, Daniel Gröber escreveu:

Hi Lucas,

On Tue, Mar 05, 2024 at 03:29:49PM -0300, Lucas Castro wrote:

Are you sure you want to change the source package name? Doing so

fractures

the history of the package on tracker.d.o and it's not really

necessary.

The upstream has changed software name but it's a good point about
tracker.d.o.

Right, so users will try to `apt install foolsm` in the future, but

the

source package name is largeley irellevant to them.


Quick package review:

 - d/postinst: I don't think it's useful to print the message

about editing

   the config. I've only seen packages do that in special

circumstances, do

   you have a justification for it being necessary here?

Really, really not. I really would like improve that, I guess to

write good

doc and manual pages is enough.

I would argue users (sysadmins in this case) are going to be

familiar with

the concept of having to configure a package before it becomes

useful and

while the daemon not being started at package installation is
unconventional in Debian automatic config reloading is by far not

universal

so any config change to make lsm useful is going to elicit a restart
anyway.

So I just don't see why we'd want a conspicuous message telling

people what

they already know :)


 - You declare Replaces+Conflicts on lsm but you don't seem to

take any

   care for the new binary package to actually be compatible

with the old

   one since the config location changed.

I'm in doubt, when the old config exist, if set dpkg to copy the

old config

from old location to the new one or if I just print/show up a

message to

users notifying about path update requirement.

I think an automatic upgrade is the way to go in this case as long

as the

config format is still fully compatible to the old lsm-1.0.4, but

since

copying will leave cruft behind for the user to cleanup manually I

think we

should mv the config.


If it's good/allowed do the copy, it could be applied in postinst.

I think

print/show up message is rightest way.

Consider that people upgrade Debian systems for many, many years

without

reinstalling. So every bit of cruft we leave behind due to

transitions such

as this accumulates. I don't see a technical need for not doing so

in this

case so I think we should clean up behind ourselves and move the

config to

the new location.

You should then absoluteley print a message in the log to note this

fact,

but perhaps not as conspicuously as you're printing the "configure

me"

message. Something like "Moving $OLD_PATH to $NEW_PATH" should

suffice

since the package(s) involved should be obvious from the filenames.

Just uploaded to mentors again, now the update occur smoothly.



--Daniel

Thanks for taking time on testing update.


OpenPGP_0x42F79A5E0A4D5598.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064297: RFS: foolsm/1.0.21-1 -- Link connectivity monitor tool

[Lucas Castro]

Em 23/03/2024 13:08, Tobias Frost escreveu:

Control: tags -1 moreinfo

The source package name is still being renamed, and the source package
rename is not explictly stated in the changelog.


Source package already kept old project name, only binary renamed.


I had talked about the source package rename on IRC, and no problem was 
pointed as serious then the my conclusion it wasn't going to be a problem.


But, by the way, it's going to be kept as it was.



(I think this renane shouldn't be done, to keep the history of the
package, not only the tracker but also the BTS and all the other
services working on source packages.)

(You should also bump the timestamp in the d/changelog, when uploading a
new package to mentors.)

Timestamp bumped.


The patch in package should be fowarded; as it only changes *comments*,
consider dropping it completly.


Dropped the patch, ASAP I'll forward to upstream.


Already uploaded to mentors.



--
tobi


Thanks Tobias.




On Thu, 14 Mar 2024 22:25:04 -0300 Lucas Castro 
wrote:

Em 06/03/2024 05:49, Daniel Gröber escreveu:

Hi Lucas,

On Tue, Mar 05, 2024 at 03:29:49PM -0300, Lucas Castro wrote:

Are you sure you want to change the source package name? Doing so

fractures

the history of the package on tracker.d.o and it's not really

necessary.

The upstream has changed software name but it's a good point about
tracker.d.o.

Right, so users will try to `apt install foolsm` in the future, but

the

source package name is largeley irellevant to them.


Quick package review:

     - d/postinst: I don't think it's useful to print the message

about editing

   the config. I've only seen packages do that in special

circumstances, do

   you have a justification for it being necessary here?

Really, really not. I really would like improve that, I guess to

write good

doc and manual pages is enough.

I would argue users (sysadmins in this case) are going to be

familiar with

the concept of having to configure a package before it becomes

useful and

while the daemon not being started at package installation is
unconventional in Debian automatic config reloading is by far not

universal

so any config change to make lsm useful is going to elicit a restart
anyway.

So I just don't see why we'd want a conspicuous message telling

people what

they already know :)


     - You declare Replaces+Conflicts on lsm but you don't seem to

take any

   care for the new binary package to actually be compatible

with the old

   one since the config location changed.

I'm in doubt, when the old config exist, if set dpkg to copy the

old config

from old location to the new one or if I just print/show up a

message to

users notifying about path update requirement.

I think an automatic upgrade is the way to go in this case as long

as the

config format is still fully compatible to the old lsm-1.0.4, but

since

copying will leave cruft behind for the user to cleanup manually I

think we

should mv the config.


If it's good/allowed do the copy, it could be applied in postinst.

I think

print/show up message is rightest way.

Consider that people upgrade Debian systems for many, many years

without

reinstalling. So every bit of cruft we leave behind due to

transitions such

as this accumulates. I don't see a technical need for not doing so

in this

case so I think we should clean up behind ourselves and move the

config to

the new location.

You should then absoluteley print a message in the log to note this

fact,

but perhaps not as conspicuously as you're printing the "configure

me"

message. Something like "Moving $OLD_PATH to $NEW_PATH" should

suffice

since the package(s) involved should be obvious from the filenames.

Just uploaded to mentors again, now the update occur smoothly.



--Daniel

Thanks for taking time on testing update.


OpenPGP_0x42F79A5E0A4D5598.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064297: RFS: foolsm/1.0.21-1 -- Link connectivity monitor tool

[Lucas Castro]

Em 06/03/2024 05:49, Daniel Gröber escreveu:

Hi Lucas,

On Tue, Mar 05, 2024 at 03:29:49PM -0300, Lucas Castro wrote:

Are you sure you want to change the source package name? Doing so fractures
the history of the package on tracker.d.o and it's not really necessary.

The upstream has changed software name but it's a good point about
tracker.d.o.

Right, so users will try to `apt install foolsm` in the future, but the
source package name is largeley irellevant to them.


Quick package review:

   - d/postinst: I don't think it's useful to print the message about editing
 the config. I've only seen packages do that in special circumstances, do
 you have a justification for it being necessary here?

Really, really not. I really would like improve that, I guess to write good
doc and manual pages is enough.

I would argue users (sysadmins in this case) are going to be familiar with
the concept of having to configure a package before it becomes useful and
while the daemon not being started at package installation is
unconventional in Debian automatic config reloading is by far not universal
so any config change to make lsm useful is going to elicit a restart
anyway.

So I just don't see why we'd want a conspicuous message telling people what
they already know :)


   - You declare Replaces+Conflicts on lsm but you don't seem to take any
 care for the new binary package to actually be compatible with the old
 one since the config location changed.

I'm in doubt, when the old config exist, if set dpkg to copy the old config
from old location to the new one or if I just print/show up a message to
users notifying about path update requirement.

I think an automatic upgrade is the way to go in this case as long as the
config format is still fully compatible to the old lsm-1.0.4, but since
copying will leave cruft behind for the user to cleanup manually I think we
should mv the config.


If it's good/allowed do the copy, it could be applied in postinst. I think
print/show up message is rightest way.

Consider that people upgrade Debian systems for many, many years without
reinstalling. So every bit of cruft we leave behind due to transitions such
as this accumulates. I don't see a technical need for not doing so in this
case so I think we should clean up behind ourselves and move the config to
the new location.

You should then absoluteley print a message in the log to note this fact,
but perhaps not as conspicuously as you're printing the "configure me"
message. Something like "Moving $OLD_PATH to $NEW_PATH" should suffice
since the package(s) involved should be obvious from the filenames.


Just uploaded to mentors again, now the update occur smoothly.




--Daniel


Thanks for taking time on testing update.


Lucas Castro.



OpenPGP_0x42F79A5E0A4D5598.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064297: RFS: foolsm/1.0.21-1 -- Link connectivity monitor tool

[Lucas Castro]

Em 05/03/2024 08:09, Daniel Gröber escreveu:

Hi Lucas,

On Mon, Feb 19, 2024 at 04:50:27PM -0300, Lucas Castro wrote:

  * Package name : foolsm

Are you sure you want to change the source package name? Doing so fractures
the history of the package on tracker.d.o and it's not really necessary.


The upstream has changed software name but it's a good point about 
tracker.d.o.


I'll take a look at some project that has changed the name too, BTW I 
already looked at some of them but not checked the source package name.




Quick package review:

  - d/postinst: I don't think it's useful to print the message about editing
the config. I've only seen packages do that in special circumstances, do
you have a justification for it being necessary here?
Really, really not. I really would like improve that, I guess to write 
good doc and manual pages is enough.

  - You declare Replaces+Conflicts on lsm but you don't seem to take any
care for the new binary package to actually be compatible with the old
one since the config location changed.


I'm in doubt, when the old config exist, if set dpkg to copy the old 
config from old location to the new one or if I just print/show up a 
message to users notifying about path update requirement.


If it's good/allowed do the copy, it could be applied in postinst. I 
think print/show up message is rightest way.



  - d/foolsm.init: Still has the old $CONFIG path

That's true, I'll update and re-upload.


--Daniel


OpenPGP_0x42F79A5E0A4D5598.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1064297: RFS: foolsm/1.0.21-1 -- Link connectivity monitor tool

[Lucas Castro]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "foolsm":

 * Package name : foolsm
   Version  : 1.0.21-1
   Upstream contact : [fill in name and email of upstream]
 * URL  :http://lsm.foobar.fi/
 * License  : GPL-2
 * Vcs  : [fill in URL of packaging vcs]
   Section  : utils

The source builds the following binary packages:

  foolsm - Link connectivity monitor tool
  lsm - Link connectivity monitor tool - transitional package

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

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

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

  dget 
-xhttps://mentors.debian.net/debian/pool/main/f/foolsm/foolsm_1.0.21-1.dsc

Changes for the initial release:

 foolsm (1.0.21-1) unstable; urgency=medium
 .
   * New upstream release
   * debian/watch updated
   * debian/patches/ cleaned out

Regards,
--
  Lucas Castro



OpenPGP_0x42F79A5E0A4D5598.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1054086: lsm: let dh_installsystemd choose the location of units

[Lucas Castro]

Em 24/01/2024 03:22, Helmut Grohne escreveu:

On Tue, Jan 23, 2024 at 05:25:21PM -0300, Lucas Castro wrote:

dh_installsystemd look only for maintainer scripts. That means it looks only
for scripts residing in debian/ folder.

I guess you should know about that, therefore you propose to create a
symlink from systemd file provided by upstream.

That's not the reason for proposing the change. The reason is that we
need to move the units from /lib/systemd/system to
/usr/lib/systemd/system in trixie but not bookworm. Encoding this in a
debian/*.install file is not simple, but we updated dh_installsystemd to
do exactly that.


systemd file .service will be moved to the /usr/lib/systemd/system 
folder and close this bug.






Sorry, I'm not going to apply the solution proposed on the next release, but
I take a look what it should be the best approach for this.

I do not insist on using my approach. It merely is the one I considered
most suitable at the time of submitting the bug. Alternatively, you may
employ dh_movetousr or update the location in debian/lsm.install (though
extra work is required in case of backporting for the last option). The
point of this bug is to not ship aliased locations such as /lib.

Helmut



OpenPGP_0x42F79A5E0A4D5598.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1041221: lsm: Please package upstream version 1.0.24

[Lucas Castro]

Em 15/07/2023 15:52, Daniel Gröber escreveu:

Source: lsm
Severity: wishlist
X-Debbugs-Cc: d...@darkboxed.org

Hi Lucas,

it looks like there haven't been any uploads of lsm since 2020. The
version we currently have in Debian is 1.0.4 but upstream has been
busy and is at version 1.0.24.


I guess you mean 1.0.21. The upload is planned for next.



Unfortunately it's unclear what changes have been made upstream since
neither a changelog nor a git repo are provided. Still it's best to
keep packages up-to-date.

If you're not interested in maintaining lsm anymore I might be
interested in taking over, though I'm evaluating if lsm covers my
use-case :)

Thanks,
--Daniel



Thanks,

Lucas Castro.

Bug#1054086: lsm: let dh_installsystemd choose the location of units

[Lucas Castro]

Hello Helmut,

Em 16/10/2023 15:11, Helmut Grohne escreveu:

Source: lsm
Version: 1.0.4-2
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

We want to move aliased files from / to /usr to finalize the /usr-merge
transition via DEP17. lsm is involved, because it installs a systemd
unit. Rather than move the unit, I recommend installing it using
dh_installsystemd, because that'll automatically revert back to the old
location for bookworm-backports and thus honour the moratorium that
still is in effect there. debdiff cannot represent this patch:

 rm debian/lsm.install
 ln -s ../lsm.service debian/lsm.service


I'm planing upload a new version next week.

dh_installsystemd look only for maintainer scripts. That means it looks 
only for scripts residing in debian/ folder.


I guess you should know about that, therefore you propose to create a 
symlink from systemd file provided by upstream.


Sorry, I'm not going to apply the solution proposed on the next release, 
but I take a look what it should be the best approach for this.





Helmut



Regards,

Lucas Castro.

Bug#1054086: lsm: let dh_installsystemd choose the location of units

[Lucas Castro]

Em 08/12/2023 18:09, Chris Hofstaedtler escreveu:

Hi Lucas,


Em 16 de outubro de 2023 15:11:55 BRT, Helmut Grohne  
escreveu:

Source: lsm

[..]

still is in effect there. debdiff cannot represent this patch:

rm debian/lsm.install
ln -s ../lsm.service debian/lsm.service

* Lucas Castro :

Sorry about delay for "fixing" that.

ASAP I'll work on that.

Are there any blockers I might be able to help you with, to move
this forward?


I was little busy working on myself workflow. In two week it'll be "fix it".

I just need to discuss about changing the package name.



Thanks,
Chris

Bug#1054086: lsm: let dh_installsystemd choose the location of units

[Lucas Castro]

Sorry about delay for "fixing" that.

ASAP I'll work on that.  

Em 16 de outubro de 2023 15:11:55 BRT, Helmut Grohne  
escreveu:
>Source: lsm
>Version: 1.0.4-2
>Tags: patch
>User: helm...@debian.org
>Usertags: dep17m2
>
>We want to move aliased files from / to /usr to finalize the /usr-merge
>transition via DEP17. lsm is involved, because it installs a systemd
>unit. Rather than move the unit, I recommend installing it using
>dh_installsystemd, because that'll automatically revert back to the old
>location for bookworm-backports and thus honour the moratorium that
>still is in effect there. debdiff cannot represent this patch:
>
>rm debian/lsm.install
>ln -s ../lsm.service debian/lsm.service
>
>Helmut
>

Bug#1041221: lsm: Please package upstream version 1.0.24

[Lucas Castro]

Em 15/07/2023 15:52, Daniel Gröber escreveu:

Source: lsm
Severity: wishlist
X-Debbugs-Cc: d...@darkboxed.org

Hi Lucas,

it looks like there haven't been any uploads of lsm since 2020. The
version we currently have in Debian is 1.0.4 but upstream has been
busy and is at version 1.0.24.


I'll be working on this until the end of the month, but my guess about 
this one is it should be renamed.




Unfortunately it's unclear what changes have been made upstream since
neither a changelog nor a git repo are provided. Still it's best to
keep packages up-to-date.

If you're not interested in maintaining lsm anymore I might be
interested in taking over, though I'm evaluating if lsm covers my
use-case :)

Don't worry about this package, it's a really simple package maintenance.


Thanks,
--Daniel


OpenPGP_signature
Description: OpenPGP digital signature

Bug#834050: libpam-ldap: please make the build reproducible

[Lucas Castro]

Thanks. = )

Em 17/11/2022 16:48, Vagrant Cascadian escreveu:

Control: tags 834050 pending

On 2017-02-15, Chris Lamb wrote:

Lucas Castro wrote:


I suppose the patch hadn't fixed the bug.

Ah, try:

   --- libpam-ldap-186.orig/vers_string
   +++ libpam-ldap-186/vers_string
   @@ -14,6 +14,10 @@ if ($ENV{'PROGRAM'}) { $PROGRAM = $ENV{'
  
chop($AUTHOR);

chop($DATE=`date -u`);
   +if (defined $ENV{SOURCE_DATE_EPOCH}) {
   +chop($DATE=`LC_ALL=C date --date="@\${SOURCE_DATE_EPOCH}" -u`);
   +$AUTHOR="NO DEVELOPER SET";
   +}
chop($CWD=`pwd`);
  
($PROJECT, $VERSION) = split(/\-/, ());

This solved both the timestamp and build user issue!

There was another issue where the package and version information is
derived from the top-level build directory, but this can be fixed easily
by passing PROGRAM to dh_auto_build.

Uploaded an NMU to DELAYED/10 which fixes both outstanding issues:

diff -Nru libpam-ldap-186/debian/changelog libpam-ldap-186/debian/changelog
--- libpam-ldap-186/debian/changelog2017-05-31 10:19:41.0 -0700
+++ libpam-ldap-186/debian/changelog2022-11-17 11:42:13.0 -0800
@@ -1,3 +1,17 @@
+libpam-ldap (186-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Chris Lamb ]
+  * vers_string: Use fixed value for AUTHOR if SOURCE_DATE_EPOCH is
+set. (Closes: #834050)
+
+  [ Vagrant Cascadian ]
+  * debian/rules: Pass PROGRAM to dh_auto_build override.
+(Closes: #834050)
+
+ -- Vagrant Cascadian   Thu, 17 Nov 2022 
11:42:13 -0800
+
  libpam-ldap (186-4) unstable; urgency=medium
  
* Install /usr/share/pam-configs/ldap

diff -Nru libpam-ldap-186/debian/patches/series 
libpam-ldap-186/debian/patches/series
--- libpam-ldap-186/debian/patches/series   2017-02-10 20:39:24.0 
-0800
+++ libpam-ldap-186/debian/patches/series   2022-11-17 11:42:13.0 
-0800
@@ -6,3 +6,4 @@
  reproducible_build.patch
  configfile_install.patch
  configfile_references.patch
+vers_string-use-fixed-value-for-author-i.patch
diff -Nru 
libpam-ldap-186/debian/patches/vers_string-use-fixed-value-for-author-i.patch 
libpam-ldap-186/debian/patches/vers_string-use-fixed-value-for-author-i.patch
--- 
libpam-ldap-186/debian/patches/vers_string-use-fixed-value-for-author-i.patch   
1969-12-31 16:00:00.0 -0800
+++ 
libpam-ldap-186/debian/patches/vers_string-use-fixed-value-for-author-i.patch   
2022-11-17 11:42:13.0 -0800
@@ -0,0 +1,21 @@
+From: Chris Lamb 
+Date: Wed, 15 Feb 2017 17:12:58 +1300
+X-Dgit-Generated: 186-4.1 98efdb0f8a716ed9c1403523c90f3b0b6ff8c493
+Subject: vers_string: Use fixed value for AUTHOR if SOURCE_DATE_EPOCH is set.
+
+(Closes: #834050)
+
+---
+
+diff --git a/vers_string b/vers_string
+index 11af68a..5a072f3 100755
+--- a/vers_string
 b/vers_string
+@@ -16,6 +16,7 @@ chop($AUTHOR);
+ chop($DATE=`date -u`);
+ if (defined $ENV{SOURCE_DATE_EPOCH}) {
+   chop($DATE=`LC_ALL=C date --date="@\${SOURCE_DATE_EPOCH}" -u`);
++  $AUTHOR="NO DEVELOPER SET";
+ }
+ chop($CWD=`pwd`);
+
diff -Nru libpam-ldap-186/debian/rules libpam-ldap-186/debian/rules
--- libpam-ldap-186/debian/rules2017-05-31 10:19:28.0 -0700
+++ libpam-ldap-186/debian/rules2022-11-17 11:42:13.0 -0800
@@ -4,6 +4,8 @@
  
  export DEB_BUILD_MAINT_OPTIONS= hardening=+bindnow
  
+include /usr/share/dpkg/pkg-info.mk

+
  %:
dh $@ --with autoreconf
  
@@ -17,3 +19,6 @@

dh_install
install -D -m 644 debian/libpam-ldap.pam-auth-update \
debian/libpam-ldap/usr/share/pam-configs/ldap
+
+override_dh_auto_build:
+   dh_auto_build -- PROGRAM=$(DEB_SOURCE)-$(DEB_VERSION_UPSTREAM)



live well,
   vagrant


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1014512: freeipa: FTBFS: AttributeError: module 'collections' has no attribute 'Iterable'

[Lucas Castro]

On Thu, 07 Jul 2022 12:51:31 +0200 Andreas Beckmann  wrote:
> Package: freeipa
> Version: 4.9.8-1+exp1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in 
the past)

>
> Hi,
>
> freeipa recently started to FTBFS in experimental (but not in sid) after
> some (transitive) build dependency got upgraded:
>
> ...
> Making all in css
> make[5]: Entering directory '/build/freeipa-4.9.8/install/ui/css'
> python3 -m lesscpy -x ../less/ipa.less > ipa.css
> Traceback (most recent call last):
>   File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main
> return _run_code(code, main_globals, None,
>   File "/usr/lib/python3.10/runpy.py", line 86, in _run_code
> exec(code, run_globals)
>   File "/usr/lib/python3/dist-packages/lesscpy/__main__.py", line 4, 
in 

> run()
>   File "/usr/lib/python3/dist-packages/lesscpy/scripts/compiler.py", 
line 176, in run

> p.parse(filename=args.target, debuglevel=args.debug)
>   File "/usr/lib/python3/dist-packages/lesscpy/lessc/parser.py", line 
153, in parse

> self.result = self.parser.parse(
>   File "/usr/lib/python3/dist-packages/ply/yacc.py", line 333, in parse
> return self.parseopt_notrack(input, lexer, debug, tracking, 
tokenfunc)
>   File "/usr/lib/python3/dist-packages/ply/yacc.py", line 1120, in 
parseopt_notrack

> p.callable(pslice)
>   File "/usr/lib/python3/dist-packages/lesscpy/lessc/parser.py", line 
259, in p_statement_import

> recurse.parse(filename=filename, debuglevel=0)
>   File "/usr/lib/python3/dist-packages/lesscpy/lessc/parser.py", line 
156, in parse

> self.post_parse()
>   File "/usr/lib/python3/dist-packages/lesscpy/lessc/parser.py", line 
171, in post_parse

> self.result = list(utility.flatten(out))
>   File "/usr/lib/python3/dist-packages/lesscpy/lessc/utility.py", 
line 28, in flatten
> if isinstance(elm, collections.Iterable) and not isinstance(elm, 
string_types):

> AttributeError: module 'collections' has no attribute 'Iterable'
> make[5]: *** [Makefile:660: ipa.css] Error 1
> make[5]: Leaving directory '/build/freeipa-4.9.8/install/ui/css'
> ...
>
> Andreas

Not really a freeipa related bug.

collections.Iterable
:1: DeprecationWarning: Using or importing the ABCs from 
'collections' instead of from 'collections.abc' is deprecated since 
Python 3.3, and in 3.10 it will stop working



python3-lesscpy install 
/usr/lib/python3/dist-packages/lesscpy/lessc/utility.py file.


lessc utility.py in turn import collections.Iterable that must be 
changed to collections.abc.Iterable.

Bug#1016126: freeipa-server required libndr.so.1 and it's present only on Debian stable version

[Lucas Castro]

Package: freeipa-server
Version: 4.9.8-1+exp1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: lu...@gnuabordo.com.br

Dear Maintainer,

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

   * What led up to the situation?

I tried to install freeipa-server just for testing environment.
The environment is Debian fresh installation in lxc container.

Installation ends up with an error when it try to create the REALM 
kdb5_util: Unable to load requested database module 'ipadb.so': plugin symbol 
'kdb_function_table' not found while creating database 
'/var/lib/krb5kdc/principal'

So I investigated the library required by ipadb.so 
ldd /usr/lib/x86_64-linux-gnu/krb5/plugins/kdb/ipadb.so
 it's noticed libndr.so.1 is required and not present. 
 The required library is present by samba-libs on Debian bullseye, the
 stable version by now. 

 Unstable and Sid version install libndr.so.2 in turn. 


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


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

Kernel: Linux 5.10.0-10-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages freeipa-server depends on:
ii  389-ds-base 2.0.15-1+b1
ii  acl 2.3.1-1
ii  adduser 3.123
ii  apache2 2.4.54-2
ii  certmonger  0.79.15-1+b2
ii  chrony  4.2-2
ii  fonts-font-awesome  5.0.10+really4.7.0~dfsg-4.1
ii  fonts-open-sans 1.11-2
ii  freeipa-client  4.9.8-1+exp1
ii  freeipa-common  4.9.8-1+exp1
ii  gssproxy0.8.4-2
ii  krb5-admin-server   1.20-1
ii  krb5-kdc1.20-1
ii  krb5-kdc-ldap   1.20-1
ii  krb5-otp1.20-1
ii  krb5-pkinit 1.20-1
ii  ldap-utils  2.5.12+dfsg-2
ii  libapache2-mod-auth-gssapi  1.6.3-1+b1
ii  libapache2-mod-lookup-identity  1.0.0-1
ii  libapache2-mod-wsgi-py3 4.9.0-1+b1
ii  libc6   2.33-8
ii  libgssapi-krb5-21.20-1
ii  libjs-dojo-core 1.15.4+dfsg1-1
ii  libjs-jquery3.6.0+dfsg+~3.5.13-1
ii  libjs-scriptaculous 1.9.0-2.1
ii  libk5crypto31.20-1
ii  libkrad01.20-1
ii  libkrb5-3   1.20-1
ii  libldap-2.4-2   2.4.59+dfsg-1+b1
ii  libnss3-tools   2:3.81-1
ii  libpopt01.18-3
ii  libpwquality1   1.4.4-1+b1
ii  libsasl2-modules-gssapi-mit 2.1.28+dfsg-6
ii  libssl1.1   1.1.1o-1
ii  libsss-certmap0 2.7.3-1
ii  libsss-nss-idmap0   2.7.3-1
ii  libtalloc2  2.3.3-4
ii  libunistring2   1.0-1
ii  libuuid12.38-5
ii  libverto1   0.3.1-1
ii  libwbclient02:4.16.3+dfsg-1
ii  oddjob  0.34.7-1
ii  p11-kit 0.24.1-1
ii  pki-ca  11.0.3-4
ii  pki-kra 11.0.3-4
ii  python3 3.10.5-3
ii  python3-dateutil2.8.1-6
ii  python3-gssapi  1.6.12-2+b1
ii  python3-ipaserver   4.9.8-1+exp1
ii  python3-ldap3.4.0-2+b1
ii  python3-systemd 234-4+b1
ii  samba-libs  2:4.16.3+dfsg-1
ii  slapi-nis   0.56.7-1
ii  ssl-cert1.1.2
ii  sssd-dbus   2.7.3-1
ii  systemd-sysv251.3-1

Versions of packages freeipa-server recommends:
ii  freeipa-server-dns  4.9.8-1+exp1

freeipa-server suggests no packages.

-- no debconf information

Bug#916191: /usr/lib/postfix/sbin/smtpd: Sometimes smtpd unable to authenticate a client via SASL GSSAPI

[Lucas Castro]

Hello, I was trying this bug,

I guess there is no bug right here.

On Tue, 11 Dec 2018 10:28:39 +0500 Igor Goldenberg 
 wrote:> Package: postfix


> Version: 3.1.8-0+deb9u1
> Severity: important
> File: /usr/lib/postfix/sbin/smtpd
>
> Dear Maintainer,
>
> after upgrading Debian from 8/jessie to 9/stretch I've started to
> receive periodical errors while client tries to send an email with
> authentication via Kerberos/GSSAPI via Postfix.
>
> The MUA is a Thunderbird 60.2.1 on Windows Server 2016 in AD domain.
> Thunderbird setted up to use STARTTLS with Kerberos / GSSAPI
> authentication method. Sometimes client got Kerberos error (ticket
> Kerberos/GSSAPI was not received by SMTP server) in the MUA and in the
> log I can see:
>
> Dec 11 09:40:00 mx1 postfix/smtpd[9857]: warning: SASL authentication 
failure: Requested identity not authenticated identity
> Dec 11 09:40:00 mx1 postfix/smtpd[9857]: warning: 
unknown[192.168.1.3]: SASL GSSAPI authentication failed: authentication 
failure

>
> About 4-5% of total authenticaions has such error (~20 of total ~500 in
> a day). If user in the Thunderbird close error window and try to send
> an email again it usually sends successfully. It's non needed to relog on
> the windows server or restart a mail client, just do another try.
>
> Kerberos authentication also used in the Cyrus IMAP server on the same
> Debian host and there are no any errors with Kerberos at all. So I think
> something wrong on the Postfix side.
>
> Here is the SASL source code where this error ("Requested identity not
> authenticated identity") rises.
>
> File lib/common.c, begining from line 2625:
>
> static int
> _sasl_proxy_policy(sasl_conn_t *conn,
> void *context __attribute__((unused)),
> const char *requested_user, unsigned rlen,
> const char *auth_identity, unsigned alen,
> const char *def_realm __attribute__((unused)),
> unsigned urlen __attribute__((unused)),
> struct propctx *propctx __attribute__((unused)))
> {
> if (!conn)
> return SASL_BADPARAM;
>
> if (!requested_user || *requested_user == '\0')

> return SASL_OK;

Over here you can check if the client (MUA) not send a user 
(request_user), it just return SASL_OK.


mutt as example,

    set smtp_url = 'smtp://postfix00.zw.local:25/'

if set  just as above, no request_user exist.

but instead of that it is set

    set smtp_url = 'smtp://u...@postfix00.zw.local:25/'

so the authentication will get into next step.

>
> if (!auth_identity || !requested_user || rlen != alen ||
> (memcmp(auth_identity, requested_user, rlen) != 0)) {
> sasl_seterror(conn, 0,
> "Requested identity not authenticated identity");
> RETURN(conn, SASL_BADAUTH);
> }
>
> return SASL_OK;

> }

So if the request user at smtp_url differ from sasl authenticated user 
it stops and return error.


>

> I think Postfix incorrectly use or 'auth_identity' or 'requested_user'


I really make up this setup and test both situation.

I think it's good to set this "bug" as not a bug.

--
Lucas Castro

Bug#970246: RFS: lsm/1.0.4-2 [RC] -- Link connectivity monitor tool

[Lucas Castro]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "lsm":

* Package name : lsm
Version : 1.0.4-2
Upstream Author : [fill in name and email of upstream]
* URL : http://lsm.foobar.fi/
* License : GPL-2
Section : utils

It builds those binary packages:

lsm - Link connectivity monitor tool

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


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

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

dget -x https://mentors.debian.net/debian/pool/main/l/lsm/lsm_1.0.4-2.dsc

Changes since the last upload:

lsm (1.0.4-2) unstable; urgency=medium
.
* Updated build-depends (Closes: #958635)
* Bumped Standards-Version to 5.4.0.
* Updated DH compat version to 12.
* Updated maintainer e-mail address.
* Removed unused patch, scripts_path.path file.

Regards,

--
Lucas Castro

Bug#834050: libpam-ldap: please make the build reproducible

[Lucas Castro]

On 9/2/20 7:52 PM, Chris Lamb wrote:

Hi Lucas,


I'm little busy this days,

If someone could make patch, please make a NMU.

I think I will personally refrain from doing an NMU for such an
important security-related package for this issue, but thank you for
the 'go ahead'.

Indeed, given the importance of this package, is it ridiculous to suggest 
seeking a co-maintainer on debian-devel?

Of course not.

Regards,

--
   ,''`.
  : :'  : Chris Lamb
  `. `'`  la...@debian.org  chris-lamb.co.uk
`-


--
Lucas Castro

Bug#834050: libpam-ldap: please make the build reproducible

[Lucas Castro]

I'm little busy this days,

If someone could make patch, please make a NMU.


On 9/1/20 7:53 PM, Chris Lamb wrote:

Chris Lamb wrote:


[..]

Gentle ping on this?


Regards,


--
Lucas Castro

Bug#863201: libpam-ldap not longer installs the file /usr/share/pam-configs/ldap needed for pam-auth-update

[Lucas Castro]

I've uploaded libpam-ldap to mentors,

Sorry for delay.


Em 29-05-2017 12:09, Julián Moreno Patiño escreveu:
> Control: -1 + pending patch
>
> I've uploaded libpam-ldap 186-3.1 to DELAYED/5:
>   
> libpam-ldap (186-3.1) unstable; urgency=medium
>   
>   * Non-maintainer upload.
>   * Install /usr/share/pam-configs/ldap
> needed for pam-auth-update. (Closes: #863201)
>
> The full debdiff is attached.
>
>
> Regards,
>




signature.asc
Description: OpenPGP digital signature

Bug#863201: libpam-ldap not longer installs the file /usr/share/pam-configs/ldap needed for pam-auth-update

[Lucas Castro]

Thanks, I'm going to fix that.


Em 23-05-2017 09:06, Carlos Alberto Lopez Perez escreveu:
> Package: libpam-ldap
> Version: 186-3
> Severity: grave
>
>
> libpam-ldap 184-8.7 (Jessie) installed a config file on 
> /usr/share/pam-configs/ldap
> telling pam-auth-update how it should re-configure the files on /etc/pam.d 
> when the
> command pam-auth-update is executed (that the package libpam-ldap executes on 
> the
> postinstall)
>
> libpam-ldap 186-3 (Stretch) not longer installs this file
>
> jessie $ dpkg --contents libpam-ldap_184-8.7+b1_amd64.deb | grep 
> pam-configs/ldap
> -rw-r--r-- root/root   518 2014-11-08 18:35 ./usr/share/pam-configs/ldap
>
> stretch $ dpkg --contents libpam-ldap_186-3_amd64.deb | grep pam-configs
> # nothing
>
> Therefore the package on Stretch is pretty much useless for new installs.
>
> The workaround is to copy this file manually from libpam-ldap=184-8.7 
> and manually execute pam-auth-update.
>
>
> Please, bring /usr/share/pam-configs/ldap back into libpam-ldap
>

Bug#852835: ITP: sigrok-firmware-fx2lafw -- Firmware for Cypress FX2(LP) based logic analyzers

[Lucas Castro]

retitle #852835 ITP: sigrok-firmware-fx2lafw -- Firmware for Cypress
FX2(LP) based logic analyzers

owner !




signature.asc
Description: OpenPGP digital signature

Bug#852835: ITP: sigrok-firmware-fx2lafw -- Firmware for Cypress FX2(LP) based logic analyzers

[Lucas Castro]

Package: wnpp
Followup-For: Bug #852835
Owner: Lucas Castro <lu...@gnuabordo.com.br>

Bug#834050: libpam-ldap: please make the build reproducible

[Lucas Castro]

Hello,
I suppose the patch hadn't fixed the bug.

It can be check on [1].


[1]
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/libpam-ldap.html


Em 04-02-2017 20:54, Lucas Castro escreveu:
>
> Sorry, I hadn't noticed the report.
>
> Tomorrow I'm going to take a loot at it.
>
>
> --
> Lucas Castro
> Em 04-02-2017 18:00, Chris Lamb escreveu:
>>>  this patch and uploading?
>> Friendly ping on this :)
>>
>>
>> Best wishes,
>



signature.asc
Description: OpenPGP digital signature

Bug#834050: libpam-ldap: please make the build reproducible

[Lucas Castro]

Sorry, I hadn't noticed the report.

Tomorrow I'm going to take a loot at it.


--
Lucas Castro
Em 04-02-2017 18:00, Chris Lamb escreveu:
>>  this patch and uploading?
> Friendly ping on this :)
>
>
> Best wishes,



signature.asc
Description: OpenPGP digital signature

Bug#842222: Two node-babel ITPs

[Lucas Castro]

Em 30-12-2016 00:36, Pirate Praveen escreveu:
> On Fri, 30 Dec 2016 00:20:43 +0200 Adrian Bunk <b...@stusta.de> wrote:
>> Control: forcemerge -1 849291
>>
>> Hi,
>>
>> both of you sent ITPs for node-babel, please coordinate regarding who 
>> will actually package it.
> Hi Lucas,
>  
> The work I have already done is here.
> https://anonscm.debian.org/cgit/pkg-javascript/node-babel.git
>
> I'm using npm packages to bootstrap as it has circular dependencies. We
> can upload all packages together to contrib first and then move them to
> main when they work with packaged versions.
>
> I have uploaded the packages here https://people.debian.org/~praveen/babel/
>
> We need to fix rollup and lerna builds with packaged babel to move
> further. Some problems are being discussed in pkg-javascript-devel list.
>
Ok, I'll try to help in anything, the rollup is really a problem and
neither the upstream is not helping.


--
Lucas Castro




signature.asc
Description: OpenPGP digital signature

Bug#847969: RFS: libpam-ldap/186-2

[Lucas Castro]

On 18-12-2016 10:30, Andrey Rahmatullin wrote:
> On Sat, Dec 17, 2016 at 02:54:18PM -0300, Lucas Castro wrote:
>> Ready for upload.
> The changelog still says 3.6.8.
>
So, done.

-- 
Lucas Castro



signature.asc
Description: OpenPGP digital signature

Bug#847969: RFS: libpam-ldap/186-2

[Lucas Castro]

Ready for upload.


On 14-12-2016 13:36, Andrey Rahmatullin wrote:
> Please remove extra empty lines from the changelog entry.
> Why did you enable DH_VERBOSE=1?
>

Bug#847969: RFS: libpam-ldap/186-2

[Lucas Castro]

On 14-12-2016 13:36, Andrey Rahmatullin wrote:
> Please remove extra empty lines from the changelog entry.
> Why did you enable DH_VERBOSE=1?
>
Already fixed.



signature.asc
Description: OpenPGP digital signature

Bug#847969: RFS: libpam-ldap/186-2

[Lucas Castro]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "libpam-ldap"

* Package name: libpam-ldap
  Version : 186-2
  Upstream Author : [fill in name and email of upstream]
* URL : [fill in URL of upstreams web site]
* License : [fill in]
  Section : admin

It builds those binary packages:

  libpam-ldap - Pluggable Authentication Module for LDAP

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

https://mentors.debian.net/package/libpam-ldap


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

dget -x 
https://mentors.debian.net/debian/pool/main/libp/libpam-ldap/libpam-ldap_186-2.dsc


Changes since the last upload:

It fixes #844666 bug.
 

Regards,
  Lucas Castro




signature.asc
Description: OpenPGP digital signature

Bug#798278: Node-tape depends on node-has which is very small

[Lucas Castro]

I'm not sure about that,

npm2deb brings to some others, as is-callable, is-regex and one
build-dependencies, falafel.

following the falafel dependencies we get rollup and acorn as
dependencies, those are very complicating packaging.


On 04-12-2016 06:33, Ross Gammon wrote:
> Hi Lucas,
>
> How are you getting on with node-tape? We only have a month to get it into 
> Debian Stretch.
>
> For your information, the only dependency left for node-tape (as far as I 
> know) is node-has. Node has consists of the following two lines of code:
>
> var bind = require('function-bind');
> module.exports = bind.call(Function.call, Object.prototype.hasOwnProperty);
>
> It doesn't really make sense to create a whole package just for that. I was 
> planning to either patch node-tape so that it doesn't require node-has, or 
> just provide node-has as binary package of node-tape (in case other packages 
> want to use it - which I had not checked). I can't imaging node-has ever 
> changing that much upstream!
>
> Sorry for not documenting this issue earlier - busy.
>
> Regards,
>
> Ross
>




signature.asc
Description: OpenPGP digital signature

Bug#844666: libpam-ldap-186: regression: reads from the wrong conf file

[Lucas Castro]

Hello Brian,

I'm going to review the patch and the others bugs you had reported.

--
Lucas Castro
On 25-11-2016 16:51, Brian Kroth wrote:
> Brian Kroth <bpkr...@gmail.com> 2016-11-23 15:44:
>> FYI, the patch I had attached last time is wrong.  I'd just copied
>> and pasted from the old one, but that used cdbs, whereas this
>> doesn't.  I think this one should be better, though I'm no packaging
>> expert.
>>
>> Let me know if you have any comments or questions.
>>
>> Thanks,
>> Brian
>
> Ack, also missed a build depends on dh-exec in that one.
>
> Brian

Bug#798278: node-tape ITPs with different owners

[Lucas Castro]

I'm so sorry doing that,

I've not noticed that already had a ITP for that one,

I'm working on another node-* packages too.
I'll be more careful.

--
Lucas Castro

On 29-10-2016 08:38, Ross Gammon wrote:
> Hi Adrian & Lucas,
>
> I have been working on and off packaging the dependencies for
> node-tape and browserify and kosmtik for a while now.
>
> From my point of view, there are so many Node modules that need
> packaging that I don't mind someone else helping out. So whoever gets
> there first (for node-tape or its dependencies) is welcome to take
> ownership of the ITP or RFP if I was the original owner. I will see
> the bug change ownership, and if I had something half finished I will
> let you know and push what I had somewhere for you. If I don't notice,
> it shouldn't matter, because with npm2deb there isn't much time wasted.
>
> Thanks for noticing the duplication Adrian!
>
> Regards,
>
> Ross
>
>
> On 28/10/16 23:18, Adrian Bunk wrote:
>> Control: forcemerge -1 842327
>>
>> Hi Ross, hi Lucas,
>>
>> you both submitted ITPs for node-tape.
>>
>> Please coordinate and agree who will package node-tape.
>>
>> Thanks
>> Adrian
>>
>




signature.asc
Description: OpenPGP digital signature

Bug#842857: ITP: node-js-tokens -- Regex that tokenizes JavaScript

[Lucas Castro]

Package: wnpp
Severity: wishlist
Owner: Lucas Castro <lu...@gnuabordo.com.br>

* Package name: node-js-tokens
  Version : 2.0.0
  Upstream Author : Simon Lydell <>
* URL : https://github.com/lydell/js-tokens/blob/master/readme.md
* License : MIT/X
  Description : Regex that tokenizes JavaScript


 js-tokens provides a regex with the g flag that matches JavaScript
 tokens.

Bug#842327: ITP: node-tape -- tap-producing test harness for node and browsers

[Lucas Castro]

Package: wnpp
Severity: wishlist
Owner: Lucas de Castro Borges 

* Package name: node-tape
  Version : 4.6.2
  Upstream Author : James Halliday  (http://substack.net)
* URL : https://github.com/substack/tape
* License : Expat
  Programming Lang: JavaScript
  Description : tap-producing test harness for node and browsers

 .
 Node.js is an event-based server-side JavaScript engine.




signature.asc
Description: OpenPGP digital signature

Bug#842310: ITP: node-everything.js -- Contains every ECMA-262 edition 5.1 grammatical production

[Lucas Castro]

Package: wnpp
Severity: wishlist
Owner: Lucas de Castro Borges 


* Package name: node-everything.js
  Version : 1.0.3
  Upstream Author : Michael Ficarra
* URL : https://github.com/michaelficarra/everything.js
* License : BSD-3-Clause
  Programming Lang: JavaScript
  Description : Contains every ECMA-262 edition 5.1 grammatical
production


 .
 Node.js is an event-based server-side JavaScript engine.




signature.asc
Description: OpenPGP digital signature

Bug#842222: ITP: node-babel -- Generic multi-purpose compiler for JavaScript

[Lucas Castro]

Package: wnpp
Severity: wishlist
Owner: Lucas de Castro Borges 


* Package name: node-babel
  Version : 6.5.2
  Upstream Author : Sebastian McKenzie 
* URL : https://babeljs.io/
* License : Expat
  Programming Lang: JavaScript
  Description : Generic multi-purpose compiler for JavaScript

 Babel is a generic multi-purpose compiler for JavaScript.
 Using Babel you can use (and create) the next generation of JavaScript,
 as well as the next generation of JavaScript tooling.
 .
 Node.js is an event-based server-side JavaScript engine.



signature.asc
Description: OpenPGP digital signature

Bug#815319: Fix for upgrade process

[Lucas Castro]

I got the same issue,
I've been analyzing the init script and noticed that
nothing will be executed if no interfaces network is set to INTERFACES
variables
in /etc/default/isc-dhcp-server.

I've created to variables in /etc/default/isc-dhcp-server, DHCPDv4 and
DHCPDv6
and checked for true|false and then call the related command for each
variable if its enabled.

I don't think a good idea relies on setting the network interfaces for
INTERFACES variables,
because the service don't do that, it just run on the subnet that found
in config file,
if the user decided to do that he can, but it's not essential.
--- isc-dhcp-server	2016-08-08 19:11:30.639671000 -0300
+++ /etc/init.d/isc-dhcp-server	2016-08-08 19:48:57.047671000 -0300
@@ -95,7 +95,7 @@
 	DESC="$5"
 
 	shift 5
-	INTERFACES="$*"
+	#INTERFACES="$*"
 
 	test_config "$VERSION" "$CONF"
 	log_daemon_msg "Starting $DESC" "$NAME"
@@ -146,10 +146,16 @@
 		if test -n "$INTERFACESv4"; then
 			start_daemon "-4" "$DHCPDv4_CONF" "$NAME4" \
 "$DHCPDv4_PID" "$DESC4" "$INTERFACESv4"
+		else
+			start_daemon "-4" "$DHCPDv4_CONF" "$NAME4" \
+"$DHCPDv4_PID" "$DESC4" "$INTERFACESv4"
 		fi
 		if test -n "$INTERFACESv6"; then
 			start_daemon "-6" "$DHCPDv6_CONF" "$NAME6" \
 "$DHCPDv6_PID" "$DESC6" "$INTERFACESv6"
+		else
+			start_daemon "-6" "$DHCPDv6_CONF" "$NAME6" \
+"$DHCPDv6_PID" "$DESC6" "$INTERFACESv6"
 		fi
 		;;
 	stop)
@@ -170,6 +176,9 @@
 		if test -n "$INTERFACESv4"; then
 			echo -n "Status of $DESC4: "
 			check_status -v $DHCPDv4_PID $NAME4 || exit $?
+		else
+			echo -n "Status of $DESC4: "
+			check_status -v $DHCPDv4_PID $NAME4 || exit $?
 		fi
 		if test -n "$INTERFACESv6"; then
 			echo -n "Status of $DESC6: "
--- isc-dhcp-server	2016-08-08 19:11:30.639671000 -0300
+++ /etc/init.d/isc-dhcp-server	2016-08-08 20:22:18.879671000 -0300
@@ -95,7 +95,7 @@
 	DESC="$5"
 
 	shift 5
-	INTERFACES="$*"
+	#INTERFACES="$*"
 
 	test_config "$VERSION" "$CONF"
 	log_daemon_msg "Starting $DESC" "$NAME"
@@ -137,17 +137,12 @@
 
 case "$1" in
 	start)
-		if test -n "$INTERFACES" -a -z "$INTERFACESv4"; then
-echo "DHCPv4 interfaces are no longer set by the INTERFACES variable in" >&2
-echo "/etc/default/isc-dhcp-server.  Please use INTERFACESv4 instead." >&2
-echo "Migrating automatically for now, but this will go away in the future." >&2
-INTERFACESv4="$INTERFACES"
-		fi
-		if test -n "$INTERFACESv4"; then
+		if [ $DHCPD_ENABLED = true ]; then
 			start_daemon "-4" "$DHCPDv4_CONF" "$NAME4" \
 "$DHCPDv4_PID" "$DESC4" "$INTERFACESv4"
 		fi
-		if test -n "$INTERFACESv6"; then
+		if [ $DHCPDv6_ENABLED = true ]; then
+			log_progress_msg "dhcpd" "dhcpdv6 is enabled";
 			start_daemon "-6" "$DHCPDv6_CONF" "$NAME6" \
 "$DHCPDv6_PID" "$DESC6" "$INTERFACESv6"
 		fi
@@ -164,14 +159,11 @@
 		fi
 		;;
 	status)
-		if test -n "$INTERFACES" -a -z "$INTERFACESv4"; then
-INTERFACESv4="$INTERFACES"
-		fi
-		if test -n "$INTERFACESv4"; then
+		if [ $DHCPDv4_ENABLED = true ]; then 
 			echo -n "Status of $DESC4: "
 			check_status -v $DHCPDv4_PID $NAME4 || exit $?
 		fi
-		if test -n "$INTERFACESv6"; then
+		if [ $DHCPDv6_ENABLED = true ]; then
 			echo -n "Status of $DESC6: "
 			check_status -v $DHCPDv6_PID $NAME6 || exit $?
 		fi


signature.asc
Description: OpenPGP digital signature

Bug#823895: RFS: lsm/1.0.4-1

[Lucas Castro]

On 27-07-2016 14:23, Gianfranco Costamagna wrote:
> Hi,
>
>
>> Who missing? I've checked, it's okay.
>
>
> you right
>
>> About that, it's a new version with some patches I've forwarded.
>> I'll wait for this version get in Debian to investigate the new version
>> changes.
>
> I can sponsor, or wait, let me know.
If you can check what Adam Borowski had pointed, It'll be fine.
> G.
I uploaded a new version with spell patch.



signature.asc
Description: OpenPGP digital signature

Bug#823895: RFS: lsm/1.0.4-1

[Lucas Castro]

On 27-07-2016 13:14, Gianfranco Costamagna wrote:
> Lets finish the review:
> 1)
>  
> grep copyright . -Ri
>
> missing people
Who missing? I've checked, it's okay.
> 2) 
> debian/upstream/changelog
>
> what^
> 3) did you forward patches upstream?
forwarded the changelog? His changelog is merged into spec file.
>
> if you can fix/answer the above I think we are good
>
> check-all-the-things review:
> $ codespell --quiet-level=3
> ./config.c:169: unkown  ==> unknown
> ./lsm.c:137: occured  ==> occurred
> ./lsm.spec:825: lisence  ==> license, licence
It is a false-positive, because the changelog is merged into this file,
so it's fix report in changelog.
> ./debian/lsm.init:12: conection  ==> connection
> ./debian/upstream/changelog:695: lisence  ==> license, licence
this file is extract from changelog, so is the same one above.
I'll fix the others.
>
> $ find -type d \( -iname .bzr -o -iname .git -o -iname .hg -o -iname .svn -o 
> -iname CVS -o -iname RCS -o -iname SCCS -o -iname _MTN -o -iname _darcs -o 
> -iname .pc -o -iname .cabal-sandbox -o -iname .cdv -o -iname .metadata -o 
> -iname CMakeFiles -o -iname _build -o -iname _sgbak -o -iname autom4te.cache 
> -o -iname blib -o -iname cover_db -o -iname node_modules -o -iname '~.dep' -o 
> -iname '~.dot' -o -iname '~.nib' -o -iname '~.plst' \) -prune -o -type f ! \( 
> -iname '*.bak' -o -iname '*.swp' -o -iname '#.*' -o -iname '#*#' -o -iname 
> 'core.*' -o -iname '*~' -o -iname '*.gif' -o -iname '*.jpg' -o -iname 
> '*.jpeg' -o -iname '*.png' -o -iname '*.min.js' -o -iname '*.js.map' -o 
> -iname '*.js.min' -o -iname '*.min.css' -o -iname '*.css.map' -o -iname 
> '*.css.min' \) -exec env PERL5OPT=-m-lib=. spellintian --picky {} +
>
>
> $ env PERL5OPT=-m-lib=. uscan --report-status --no-verbose
> uscan: Newest version of lsm on remote site is 1.0.5, local version is 1.0.4
> uscan:=> Newer package available from
> http://lsm.foobar.fi/download/lsm-1.0.5.tar.gz
About that, it's a new version with some patches I've forwarded.
I'll wait for this version get in Debian to investigate the new version
changes.
> G.

-- 
Lucas Castro



signature.asc
Description: OpenPGP digital signature

Bug#823895: RFS: lsm/1.0.4-1

[Lucas Castro]

On 21-05-2016 11:59, Adam Borowski wrote:
> On Fri, May 20, 2016 at 10:31:49PM -0300, Lucas Castro wrote:
>> On 14-05-2016 20:45, Adam Borowski wrote:
>>> Only upon checking the syslog I see:
>>> May 15 00:30:37 umbar lsm[12853]: no targets found in config file
>>> yet according to comments in /etc/lsm/lsm.conf:
>>> # Defaults for the connection entries
>>> # These are set in the code. You may override any values here.
>>> which suggests there's no need to edit the config for basic functionality.
>>>
>>> If I read this wrong and some setup is needed, then the package shouldn't
>>> try to start the daemon on initial install, and provide a feedback that
>>> editing the config file is required.
>>>
>>> There's no documentation describing what's needed to get lsm running.
>> I'm almost fishing.
>> But I don't think I need to write a documentation how to setup
>> the config file is easy to understand, just feeding back it's needed to
>> setup to get working.
>> what do you think?
> I meant mostly what's needed to get the basics running.
My problem I didn't noticed problem about setup needed because I've
installed at a machine was already working. 
> I got the impression you're -trying- to have it work out of the box, in
> which case no action is needed.  If I'm wrong and configuration is required,
> then you need to 1. handle lack of such config gracefully, and 2. point the
> user as to what needs to be done.
I've done the most changed you pointed, either the feedback about that
setup is needed to get it running.
my question is just about user perspective, if I really need to write a
documentation how to configure or
just show to user they need to setup. Something like "Edit
/etc/lsm/lsm.conf is needed to get it running."
>
>




signature.asc
Description: OpenPGP digital signature

Bug#823895: RFS: lsm/1.0.4-1

[Lucas Castro]

On 14-05-2016 20:45, Adam Borowski wrote:
> On Sat, May 14, 2016 at 12:22:13AM -0300, Lucas Castro wrote:
>> On 13-05-2016 11:46, Adam Borowski wrote:
>>>> On 10-05-2016 02:43, Lucas Castro wrote
>>>>> I am looking for a sponsor for my package "lsm"
>>>>>
>>>>> dget -x 
>>>>> https://mentors.debian.net/debian/pool/main/l/lsm/lsm_1.0.4-1.dsc
>>> 2. The manpage seems mangled:
>>>
>>>While simple to configure, provides easy way reconfigure routes, 
>>> calling notifyscript
>>>
>>>lsmVery configurable, but doesn't support domain names yet.
>> Thanks, fixed.
> Hmm, it looks like you merely added a space and lowercased V:
>
>While simple to configure, provides easy way reconfigure routes, 
> calling notifyscript.
>
>lsm very configurable program, but doesn't support domain names yet.
>
> These two lines don't quite make sense...
>
>
>>> 3. Typo: exectuble.
>> if you mean man page typo, fixed.
> It's still in the init script, line 32.
>
>
> Too bad, when actually trying to install the package:
>
> [] Starting Link Monitor.: lsminvoke-rc.d: initscript lsm, action "start" 
> failed.
> dpkg: error processing package lsm (--install):
>  subprocess installed post-installation script returned error exit status 1
> Processing triggers for man-db (2.7.5-1) ...
> Errors were encountered while processing:
>  lsm
>
> [~]# /etc/init.d/lsm start
> [] Starting Link Monitor.: lsm[~]# echo $?
> 1
> (no newline, by the way -- init scripts shouldn't use "set -e")
>
> [~]# lsm --config /etc/lsm/lsm.conf 
> [~]# echo $?
> 1
>
> An error message describing what went wrong would be nice...
>
> Only upon checking the syslog I see:
> May 15 00:30:37 umbar lsm[12853]: no targets found in config file
> yet according to comments in /etc/lsm/lsm.conf:
> # Defaults for the connection entries
> # These are set in the code. You may override any values here.
> which suggests there's no need to edit the config for basic functionality.
>
> If I read this wrong and some setup is needed, then the package shouldn't
> try to start the daemon on initial install, and provide a feedback that
> editing the config file is required.
>
> There's no documentation describing what's needed to get lsm running.
I'm almost fishing.
But I don't think I need to write a documentation how to setup
the config file is easy to understand, just feeding back it's needed to
setup to get working.
what do you think?
>
> Also, it appears the only copy of upstream's changelog is hidden inside
> lsm.spec (lines between "%changelog" and "#EOF").  Please cut this (with sed
> or a similar tool) and install as /usr/share/doc/*/changelog.gz
>
>
> In /usr/share/doc/lsm/examples/lsm.conf.sample, there are references to
> /usr/libexec/lsm/ instead of /usr/share/lsm/, it'd be nice to sed that to
> what's installed on Debian.
>
>
>>> Meow!
>> Done.
> Hah!  This was intended as an onomatopeia not an imperative, but I really
> like your interpretation :)
>




signature.asc
Description: OpenPGP digital signature

Bug#823895: RFS: lsm/1.0.4-1

[Lucas Castro]

On 13-05-2016 11:46, Adam Borowski wrote:
>> On 10-05-2016 02:43, Lucas Castro wrote
>>> I am looking for a sponsor for my package "lsm"
>>>
>>> * Package name: lsm
>>>   Upstream Author : Mika Ilmaranta <il...@nullnet.fi>
>>> * URL : http://lsm.foobar.fi/
>>>
>>> dget -x 
>>> https://mentors.debian.net/debian/pool/main/l/lsm/lsm_1.0.4-1.dsc
> From a superficial review:
>
> 1. Please delete (or fill out) debian/README.source
removed.
> 2. The manpage seems mangled:
>
>While simple to configure, provides easy way reconfigure routes, 
> calling notifyscript
>
>lsmVery configurable, but doesn't support domain names yet.
Thanks, fixed.
>
> 3. Typo: exectuble.
if you mean man page typo, fixed.
>
> Meow!
Done.



signature.asc
Description: OpenPGP digital signature

Bug#823895: RFS: lsm/1.0.4-1

[Lucas Castro]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

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

* Package name: lsm
  Version : 1.0.4-1
  Upstream Author : Mika Ilmaranta 
* URL : http://lsm.foobar.fi/
* License : GPL-2
  Section : utils

  It builds those binary packages:

lsm   - Link connectivity monitor tool

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

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


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

dget -x https://mentors.debian.net/debian/pool/main/l/lsm/lsm_1.0.4-1.dsc




signature.asc
Description: OpenPGP digital signature

Bug#819554: RFA: libpam-ldap -- Pluggable Authentication Module for LDAP

[Lucas Castro]

Package: wnpp
Severity: normal

I request an adopter for the libpam-ldap package.

I'm reviewing bugs of this package and will upload the newer version. 
 The idea is keep the retrocompatibility.

Bug#408937: libpam-ldap: Wrong configuration with ldapi://

[Lucas Castro]

I was checking this bug,
it mention the #408440 bug, that say it has on writing the config file.
Said must write 'uri ldapi://'  instead of 'host ldapi://'.
But in my tests is already writing 'uri ldapi://'

shouldn't this bug  be closed?

Bug#387891: libpam-ldap: Hyphens ("-") in Base DN are not properly escaped for use in regular expressions

[Lucas Castro]

can someone say anything about this bug,
I've been trying  to reproduce but it seems is everything fine.
I can't get the reported error.

Bug#808414: ITP: ms-sys -- Program for writing Microsoft compatible boot records

[Lucas Castro]

Package: wnpp
Severity: wishlist
Owner: Lucas Castro <lucascastrobor...@gmail.com>

* Package name: ms-sys
  Version : 0.0.28
  Upstream Author : Henrik Carlqvist <he...@users.sourceforge.net>
* URL : http://ms-sys.sourceforge.net/
* License : GPL-2+
  Programming Lang: C
  Description : Program for writing Microsoft compatible boot records

The program does the same as Microsoft "fdisk /mbr" to a hard disk
 or "sys d:" to a floppy or FAT partition except that it does not copy
 any system files, only the boot record is written.

It's usual in day-to-day of sysadmin the OS installation, 
and with this package become easier to write boot record 
for MS OSes on flashs and so create MS OS bootable flash.  
I'll maintain this package by myself. 

Bug#808414: RFS: ms-sys -- Program for writing Microsoft compatible boot records

[Lucas Castro]

Package: sponsorship-requests
Followup-For: Bug #808414

Dear Maintainer,

I'm looking for a sponsor for my package "ms-sys"

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (1001, 'testing'), (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#808414: ITP: ms-sys -- Program for writing Microsoft compatible boot records

[lucas castro]

Thanks Andrew about information,
I'll take a look at ms-sys-free.

On Sat, Dec 19, 2015 at 8:05 PM, Andrew Shadura <and...@shadura.me> wrote:

> On 19 December 2015 at 22:25, Lucas Castro <lucascastrobor...@gmail.com>
> wrote:
> > * Package name: ms-sys
> >   Version : 0.0.28
> >   Upstream Author : Henrik Carlqvist <he...@users.sourceforge.net>
> > * URL : http://ms-sys.sourceforge.net/
> > * License : GPL-2+
> >   Programming Lang: C
> >   Description : Program for writing Microsoft compatible boot records
> >
> > The program does the same as Microsoft "fdisk /mbr" to a hard disk
> >  or "sys d:" to a floppy or FAT partition except that it does not copy
> >  any system files, only the boot record is written.
> >
> > It's usual in day-to-day of sysadmin the OS installation,
> > and with this package become easier to write boot record
> > for MS OSes on flashs and so create MS OS bootable flash.
> > I'll maintain this package by myself.
>
> I'm quite certain this software can't enter Debian main, and I'm
> unsure about non-free, as in includes dumps of boot records apparently
> copyrighted by Microsoft, and even if there wasn't this they don't
> come with the complete source code.
>
> You may try packaging ms-sys-free instead, but I don't know how useful
> that package would be.
>
> --
> Cheers,
>   Andrew
>



-- 
contatos:
Celular: ( 99 ) 99143-5954 - Vivo
skype: lucasd3castro

Bug#699116: ITP: libpam-ldap -- Pluggable Authentication Module for LDAP

[Lucas Castro]

Package: wnpp
Followup-For: Bug #699116
Owner: Lucas Castro <lucascastrobor...@gmail.com>

Bug#796915: xmbmon: reference real upstream homepage

[lucas castro]

Thanks for warning Stephen.

It's already has a fix about that on mentors,
But I want to fix others issues, to request to upload.

On Tue, Aug 25, 2015 at 4:40 PM, Stephen Kitt sk...@debian.org wrote:

 Source: xmbmon
 Version: 2.05-8
 Severity: wishlist

 Dear Maintainer,

 The mbmon packages currently list their homepage as
 http://freecode.com/projects/xmbmon, but freecode.com is just a
 software catalog site and is no longer being updated.

 Please update the packages to point at
 http://www.nt.phys.kyushu-u.ac.jp/shimizu/download/download.html which
 is the real upstream homepage.

 Thanks,

 Stephen


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

 Kernel: Linux 4.0.0-2-amd64 (SMP w/8 CPU cores)
 Locale: LANG=en_GB.utf8, LC_CTYPE= (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash
 Init: sysvinit (via /sbin/init)




-- 
contatos:
Celular: ( 99 ) 9143-5954 - Vivo
skype: lucasd3castro
msn: lucascastrobor...@hotmail.com

Bug#792443: RFS: mirage/0.9.5.1-4 [QA]

[lucas castro]

All right now. Uploaded to mentors,

On Tue, Jul 14, 2015 at 10:05 PM, Eriberto Mota eribe...@debian.org wrote:

 tags 792443 moreinfo
 thanks


 Hi Lucas,

 I will try help you. My considerations:

 1. I can see some changes not registered in d/changelog. An example of
 this is DH level change (from 7 to 9). I used the 'debdiff' command to
 see the changes. Other files: debian/mirage.postinst,
 debian/patches/remove_gimp_remote.patch, debian/pycompat

 2. d/changelog:

 - I suggest you to organize better the ideas. Try to use a logical
 order. You can sort the itens by events (Added, Changed, Removed,
 Updated, etc) or by main events followed by files (debian/control,
 debian/copyright, etc). For the latter case, you can see an example
 here[1].

 - Please, remove the unnecessary double spaces.

 - Use debian/file for all files inside the debian/ directory, as
 debian/watch ans debian/patches/desktop_entry_issue.patch.

 - Use '$ spell changelog | sort -u' and '$ spell control | sort -u' to
 search for spelling errors, as 'Dependeces'.

 [1]
 http://metadata.ftp-master.debian.org/changelogs/main/l/lime-forensics/unstable_changelog

 3. d/control: you found a new upstream homepage to use in d/watch. So,
 why you removed the Homepage field from d/control?

 4. debian/copyright:

 - The updated notice in d/changelog is a bit generic because you did
 several modifications.

 - I found this text in upstream source code:

 mirage-Mirage is free software; you can redistribute it and/or modify
 mirage-it under the terms of the GNU General Public License as published by
 mirage-the Free Software Foundation; either version 3 of the License, or
 mirage-(at your option) any later version.

 mirage.py-Mirage is free software; you can redistribute it and/or modify
 mirage.py-it under the terms of the GNU General Public License as
 published by
 mirage.py-the Free Software Foundation; either version 3 of the License, or
 mirage.py-(at your option) any later version.

 So, the source code is GPL-3+, not GPL-3. You need to use the
 following command to check this situation:

 $ egrep -sriA25 '(copyright|public dom)' *

 - There are several authors in po/ directory.

 - You must to list all packagers in debian/* block. You can use the
 following command to search for all:

 $ egrep '(--|\[)' debian/changelog

 5. d/watch: your configuration produces notices about invalid
 character in version number (two underscores).

 6. You must always check the PTS[2] to search for bugs, tips etc. In
 bugs list I can see a relevant bug that you can close: #773997.

 [2] https://packages.qa.debian.org/m/mirage.html

 Thanks for your work.

 Regards,

 Eriberto


 2015-07-14 17:09 GMT-03:00 Lucas Castro lucascastrobor...@gmail.com:
  Package: sponsorship-requests
  Severity: normal
 
  Dear mentors,
 
  I am looking for a sponsor for my package mirage
 
 This orphaned packages required some lintian corrections and I had
 done,
 it already has two P lintians, but it is its homepage fields and
 signature
 that I didn't found.
 
  * Package name: mirage
Version : 0.9.5.1-4
Upstream Author : [fill in name and email of upstream]
* URL : [fill in URL of upstreams web site]
* License : [fill in]
Section : graphics
 
It builds those binary packages:
 
  mirage - fast and simple GTK+ image viewer
 
To access further information about this package, please visit the
 following URL:
 
http://mentors.debian.net/package/mirage
 
Alternatively, one can download the package with dget using this
 command:
 
  dget -x
 http://mentors.debian.net/debian/pool/main/m/mirage/mirage_0.9.5.1-4.dsc
 
More information about hello can be obtained from
 http://www.example.com.
 
Changes since the last upload:
 
  * QA upload.
  * Updated watch
  * debian/control
  - Bumped Standards-Version to 3.9.6
  - Homepage removed
  * debian/copyright updated
  * Added desktop_entry_issue.patch: Avoid
 desktop-entry-lacks-keywords-entry.
  * Build-Dependeces: added  dh-python.
 
  -- System Information:
  Debian Release: 8.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386
 
  Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
  Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8)
  Shell: /bin/sh linked to /bin/dash
  Init: systemd (via /run/systemd/system)
 
 
  --
  To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
  with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
  Archive:
 https://lists.debian.org/20150714200940.16904.7.reportbug@debian
 




-- 
contatos:
Celular: ( 99 ) 9143-5954 - Vivo
skype: lucasd3castro
msn: lucascastrobor...@hotmail.com

Bug#792443: RFS: mirage/0.9.5.1-4 [QA]

[Lucas Castro]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package mirage

   This orphaned packages required some lintian corrections and I had done, 
   it already has two P lintians, but it is its homepage fields and signature 
   that I didn't found. 

* Package name: mirage
  Version : 0.9.5.1-4
  Upstream Author : [fill in name and email of upstream]
  * URL : [fill in URL of upstreams web site]
  * License : [fill in]
  Section : graphics

  It builds those binary packages:

mirage - fast and simple GTK+ image viewer

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

  http://mentors.debian.net/package/mirage

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

dget -x 
http://mentors.debian.net/debian/pool/main/m/mirage/mirage_0.9.5.1-4.dsc

  More information about hello can be obtained from http://www.example.com.

  Changes since the last upload:

* QA upload.
* Updated watch 
* debian/control 
- Bumped Standards-Version to 3.9.6
- Homepage removed
* debian/copyright updated 
* Added desktop_entry_issue.patch: Avoid desktop-entry-lacks-keywords-entry.
* Build-Dependeces: added  dh-python.
  
-- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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


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