Bug#993587: Source Repository for Package

2023-09-14 Thread Sahib

Source Repository for Package already exists here

https://salsa.debian.org/debian/qalculate-qt


Thanks

Sheik



Bug#1051415: Noting existing ITP

2023-09-14 Thread Sahib
Sorry didn't realise there was an already an existing ITP, thanks for 
closing.


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

https://salsa.debian.org/debian/qalculate-qt


Thanks

Sheik



Bug#1051415: RFP: qalculate-qt -- QT version of Qalculate

2023-09-07 Thread Sahib

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: sahibz...@gmail.com

* Package name : qalculate-qt
Version : 4.8
Upstream Contact: https://github.com/Qalculate/qalculate-qt
* URL : https://github.com/Qalculate/qalculate-qt
* License : GPL 2.0
Programming Lang: C++
Description : QT version of Qalculate

Hi Maintainers,

Qalculate/QT is an alternative to the already packaged Qalculate/GTK and 
would

be nice to have it included in Debian.

Qalculate/GTK is already available in the following repositories
https://packages.debian.org/search?keywords=qalculate-
gtk=names=all=all

Thanks
Sheik



Bug#1017694: adduser assigns users secondary group to files/directories

2022-08-19 Thread Sahib

Package: adduser
Version: 3.126
Severity: normal
X-Debbugs-Cc: sahibz...@gmail.com

Hi Maintainers,


While testing the welcoming DIRMODE change in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014901


I've found that the new users home directory and files copied from 
*/etc/skel* are now owned by the users secondary group *(users)*


rather than being owned by the users primary group. Also found some 
applications in KDE/Plasma are now creating files/directories


owned by the users secondary group *(users)*. Is this expected behavior 
going forward?



Attached is the */etc/adduser.conf* replaced by the latest package.

New behaviour

root@Computer:~$ ls -la
total 20
drwx-- 2 testuserafter users 4096 Aug 19 15:42 .
drwxr-xr-x 5 root  root  4096 Aug 19 15:28 ..
-rw-r--r-- 1 testuserafter testuserafter    0 Aug 19 15:42 abc
-rw-r--r-- 1 testuserafter users  220 Aug 19 15:14 .bash_logout
-rw-r--r-- 1 testuserafter users 3526 Aug 19 15:14 .bashrc
-rw-r--r-- 1 testuserafter users  807 Aug 19 15:14 .profile


Old behaviour

root@Computer:/home/testuserbefore# ls -la
total 20
drwxr-xr-x 2 testuserbefore testuserbefore 4096 Aug 19 15:15 .
drwxr-xr-x 5 root   root   4096 Aug 19 15:15 ..
-rw-r--r-- 1 testuserbefore testuserbefore  220 Aug 19 15:15 .bash_logout
-rw-r--r-- 1 testuserbefore testuserbefore 3526 Aug 19 15:15 .bashrc
-rw-r--r-- 1 testuserbefore testuserbefore  807 Aug 19 15:15 .profile


Thanks

Ibaidul


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

Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages adduser depends on:
ii passwd 1:4.11.1+dfsg1-2

adduser recommends no packages.

Versions of packages adduser suggests:
ii cron 3.0pl1-149
ii liblocale-gettext-perl 1.07-4+b2
ii perl 5.34.0-5

-- debconf information:
adduser/title:
* adduser/homedir-permission: false
# /etc/adduser.conf: `adduser' configuration.
# See adduser(8) and adduser.conf(5) for full documentation.

# A commented out setting indicates that this is the default in the
# code. If you need to change those settings, remove the comment and
# make your intended change.

# The DSHELL variable specifies the default login shell on your
# system.
#DSHELL=/bin/bash

# The DHOME variable specifies the directory containing users' home
# directories.
#DHOME=/home

# If GROUPHOMES is "yes", then the home directories will be created as
# /home/groupname/user.
#GROUPHOMES=no

# If LETTERHOMES is "yes", then the created home directories will have
# an extra directory - the first letter of the user name. For example:
# /home/u/user.
#LETTERHOMES=no

# The SKEL variable specifies the directory containing "skeletal" user
# files; in other words, files such as a sample .profile that will be
# copied to the new user's home directory when it is created.
#SKEL=/etc/skel

# FIRST_SYSTEM_[GU]ID to LAST_SYSTEM_[GU]ID inclusive is the range for UIDs
# for dynamically allocated administrative and system accounts/groups.
# Please note that system software, such as the users allocated by the
# base-passwd package, may assume that UIDs less than 100 are unallocated.
#FIRST_SYSTEM_UID=100
#LAST_SYSTEM_UID=999

#FIRST_SYSTEM_GID=100
#LAST_SYSTEM_GID=999

# FIRST_[GU]ID to LAST_[GU]ID inclusive is the range of UIDs of dynamically
# allocated user accounts/groups.
#FIRST_UID=1000
#LAST_UID=5

#FIRST_GID=1000
#LAST_GID=5

# The USERGROUPS variable can be either "yes" or "no".  If "yes" each
# created user will be given their own group to use as a default.  If
# "no", each created user get the primary group defined below as
# USERS_GROUP or USERS_GID.
#USERGROUPS=yes

# Newly created users get this group as primary group if USERGROUPS
# "no", and as a supplemental group if USERGROUPS is "yes".
# Set one of the variables to reference the group. Don't set both.
#USERS_GID=100
#USERS_GROUP=users

# If DIR_MODE is set, directories will be created with the specified
# mode. Otherwise the default mode 0700 will be used.
#DIR_MODE=0700

# When creating system accounts: if SYS_DIR_MODE is set (and a home 
# location is specified), the directories will be created with the 
# specified node.  Otherwise the default mode 0755 will be used.
#SYS_DIR_MODE=0755

# If SETGID_HOME is "yes" home directories for users with their own
# group the setgid bit will be set. This was the default for
# versions << 3.13 of adduser. Because it has some bad side effects we
# no longer do this per default. If you want it nevertheless you can
# still set it here.  Note: this feature is DEPRECATED and will be
# removed in a future version of adduser; please use the DIR_MODE
# 

Bug#681656: Debian Installer hangs at Detect network hardware stage

2012-07-29 Thread Sahib Zone
I have same problem here.

Problem
==
I attempted several installs of Debian Wheezy - BusinessCard Installer
- Daily Build from
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/
between various dates but the Installer always hangs at “Detect
network hardware”. The install was performed using a cat5e cable. I
tested several Netinst Installers and the same problem exists.

I tested the Installer using the following commands
$ Install
$ Expert install
$ Advanced options/Rescue mode
$ Advanced options/Expert install
$ Advanced options/Graphical Expert install

Ctrl+C and Alt+F[1-4] works when “Detect network hardware” hangs.
After Ctrl+C “Detect network hardware” then runs fine and “Configure
the network” succeeds too but the Installer then hangs at “Starting up
the partition manager” at 40% progress.

Workaround
=
The bug possibly seems to be in /bin/check-missing-firmware which is
called by /bin/ethdetect

I performed the following Installer commands as a workaround
$ Advanced options/Expert install
$ Execute a shell
$ nano /bin/check-missing-firmware
Inserted “exit 0” directly after “#!/bin/sh” line
Save file
$ exit
I then ran the Installer steps as normal and the whole installation
proceeded perfectly fine. Since then Debian Wheezy has running fine
and I am able to perform daily tasks and connect to the internet as
normal ie. the workaround has so far not hindered the daily usage.

Info
===
It seems like a similar bug exists here since Debian Lenny
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509238

Thanks
Ibaidul


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



Bug#681656: Info received (Debian Installer hangs at Detect network hardware stage)

2012-07-29 Thread Sahib Zone
Also attached is a merged log file to go with
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681656#35 produced by
the following Installer actions
$ Detect network hardware
$ Pressed Ctrl+C
$ Save debug logs

Thanks
Ibaidul

On Mon, Jul 30, 2012 at 9:30 AM, Debian Bug Tracking System
ow...@bugs.debian.org wrote:

 Thank you for the additional information you have supplied regarding
 this Bug report.

 This is an automatically generated reply to let you know your message
 has been received.

 Your message is being forwarded to the package maintainers and other
 interested parties for their attention; they will reply in due course.

 Your message has been sent to the package maintainer(s):
  Debian Install System Team debian-b...@lists.debian.org

 If you wish to submit further information on this problem, please
 send it to 681...@bugs.debian.org.

 Please do not send mail to ow...@bugs.debian.org unless you wish
 to report a problem with the Bug-tracking system.

 --
 681656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681656
 Debian Bug Tracking System
 Contact ow...@bugs.debian.org with problems


DebianWheezy-BusinessCard-Installer-DailyBuild.log
Description: Binary data