hush
/
hush3
9
0
Fork 11
Code Issues 143 Pull Requests 3 Projects Releases 16 Wiki Activity
Labels Milestones
New Issue

Update debian package copyright file? #134

Open
opened 2 years ago by jahway603 · 5 comments
jahway603 commented 2 years ago
Collaborator

The copyright file has Copyright: 2016-2020, The Hush developers and not sure if this needs to be manually updated to Copyright: 2016-2022, The Hush developers or if a deb pkg creation tool does that instead.

The [copyright file](https://git.hush.is/hush/hush3/src/branch/master/contrib/debian/copyright#L2) has `Copyright: 2016-2020, The Hush developers` and not sure if this needs to be manually updated to `Copyright: 2016-2022, The Hush developers` or if a deb pkg creation tool does that instead.
duke commented 2 years ago
Owner

@jahway603 as far as I remember, it's a manually updated file, which is copied into .deb packages by the debian package creation scripts

@jahway603 as far as I remember, it's a manually updated file, which is copied into .deb packages by the debian package creation scripts
duke commented 2 years ago
Owner

@jahway603 actually, I think I was wrong and this is a manually updated file

@jahway603 actually, I think I was wrong and this is a manually updated file
jahway603 commented 2 years ago
Poster
Collaborator

@duke also just noticed that hush.is/developers is a dead link [404 status] in that same copyright file https://git.hush.is/hush/hush3/src/branch/master/contrib/debian/copyright#L5

@duke also just noticed that hush.is/developers is a dead link [404 status] in that same copyright file https://git.hush.is/hush/hush3/src/branch/master/contrib/debian/copyright#L5
duke commented 2 years ago
Owner

@jahway603 just fixed the link in dev branch

@jahway603 just fixed the link in dev branch
👍 1
duke commented 1 year ago
Owner

@jahway603 looks like we need to update the copyright years in this file manually, do you want to do that on the dev branch?

@jahway603 looks like we need to update the copyright years in this file manually, do you want to do that on the dev branch?
duke added the
documentation
 label 1 year ago
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
arm
asyncnotedecryption
danger
dev
dev-aarch64
dev-mac
dev-old-randomx
divzaddrs
dragonx
duke
freebsd
getfilterednotes
hip39
hushutils
insync
jahway603
master
mvstuff
onryo
p2p_privacy
ramhash
relaytx
rx-largepages
setbestchain
warmup
witness_cache
wolfssl
wolfssl_win
z_createrawtransaction
z_importwallet
z_signmessage
Labels
Apply labels
Clear labels
0-500 bounty
bounty up to 500 HUSH 2001-5000 bounty
bounty between 2001 and 5000 HUSH 501-2000 bounty
bounty between 501 and 2000 HUSH arm
something doesn't work on arm beginners
for new developers bug
may or may not be a bug build
problems building documentation
not enough information feature
new feature high priority
high priority i2p
related to i2p low priority
low priority medium priority
medium priority question
something is not clear release
release label or issue related to it testing
related to testing tor
related to tor wontfix
this won't be fixed
No Label 0-500 bounty 2001-5000 bounty 501-2000 bounty arm beginners bug build documentation feature high priority i2p low priority medium priority question release testing tor wontfix
Milestone
Set milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Assign users
Clear assignees
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Write Preview
Loading…
Cancel
Save
There is no content yet.
Delete Branch '%!s(MISSING)'

Deleting a branch is permanent. It CANNOT be undone. Continue?

No
Yes